API authentication - NeuDocs

The NeuDocs REST API uses firm-scoped bearer keys.

Create a key

An owner or admin opens Settings → API keys, enters a descriptive name, and creates the key. NeuDocs displays the raw key exactly once.

Copy the key immediately into a secrets manager. NeuDocs stores only its SHA-256 hash and cannot recover the raw value.

Keys begin with nd_live_. Send the key in the Authorization header:

curl https://neudocs.app/api/v1/clients \
  -H "Authorization: Bearer $NEUDOCS_API_KEY"

Responses

Missing, malformed, unknown, or revoked credentials return 401 Unauthorized.
Request validation errors return 400.
Plan/entitlement failures while creating a request return 402.
Successful JSON responses wrap results in a data property.

Scope and rotation

A key acts for its firm and currently has no per-endpoint scopes. Create separate named keys for separate systems, never embed them in browser code, and revoke unused or exposed keys immediately.