The client, server and management APIs are described in one OpenAPI 3.1 document. It is generated from the routes the API serves, so it lists exactly the endpoints, parameters and fields they have.
| File | Use it to |
|---|---|
| openapi.json | Generate a client, validate requests in tests, or import into an API tool. |
| fingerly.postman_collection.json | Explore the API in Postman, one request per operation. |
curl -O https://docs.fingerly.io/openapi.json
curl -O https://docs.fingerly.io/fingerly.postman_collection.json
What the document covers
| Tag | Operations | Key |
|---|---|---|
| Client API | Identify, deferred reports, attestation challenges | Public |
| Server API | List events, get an event | Secret |
| Management API | SDK keys, proxy keys, webhook endpoints, risk weights | Management |
- Servers are listed per region. Use the one your keys belong to.
- Each operation names the kind of key it accepts, as the
publicKey,secretKeyormanagementKeysecurity scheme. All three are sent in thex-api-keyheader. - Every error response uses the error body.
- Webhook events are not operations you call, so they are not in the document. See the event envelope.
Import into Postman
- In Postman, choose Import and select
fingerly.postman_collection.json. - Open the collection's Variables and set
baseUrl, the keys you want to use, andorganizationId. - Send Describe the management key first to read your
organizationId.
Generate a client
Any OpenAPI 3.1 generator can build a client from the document. Operation IDs are named for what the operation does, such as listEvents and issueSdkKey.
npx openapi-typescript https://docs.fingerly.io/openapi.json -o fingerly-api.d.ts
To read events and verify webhooks, the server SDKs are simpler than a generated client.
Versions
The document describes API v1. It changes only in the ways the versioning policy allows within a version, and every change is listed in the changelog. Write clients that ignore fields they do not know.