Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.dolfinai.co/llms.txt

Use this file to discover all available pages before exploring further.

​
API Key Authentication

All API requests are authenticated using the x-dolfin-api-key header. Your API key is distributed when your organisation is onboarded to the Dolfin platform. 
curl -X GET https://api.dolfinai.co/invoices \
  -H "x-dolfin-api-key: your-api-key" \
  -H "x-dolfin-organisation-id: your-org-id"

​
Required Headers

HeaderDescriptionRequired
x-dolfin-api-keyYour API keyYes (for all authenticated endpoints)
x-dolfin-organisation-idThe organisation ID to scope requests toYes (for most endpoints)
Some endpoints like creating organisations and creating users are exempt from the x-dolfin-organisation-id header requirement, as they operate across organisations.

​
Bearer Token Authentication

End users (e.g. SMB users provisioned by your platform) authenticate using Bearer JWTs. These tokens are obtained by exchanging a short-lived auth code via the POST /auth/exchange endpoint. 
curl -X GET https://api.dolfinai.co/invoices \
  -H "Authorization: Bearer eyJ..." \
  -H "x-dolfin-organisation-id: your-org-id"
Bearer tokens are valid for 8 hours and contain the user’s organisation memberships and roles as claims.

Client integration guide

See the full flow for provisioning users and generating bearer tokens.