IDfier Developers

Getting started

Credentials, base URL, authentication, responses and testing.

Get credentials

Write to support@idfier.com for a business client. IDfier sets which customer data the client may receive (its scopes) and shows the clientSecret once: store it in your server's secret store.

You need a backend that can make HTTPS requests, and a page that can show a QR code (or, on phones, a button that opens the IDfier app).

Base URL

https://api.idfier.com/api/v3

Authenticate

Send the credentials as headers on every request:

clientid: your-client-id
clientsecret: your-client-secret
Content-Type: application/json

Keep the secret on your server

Never put clientSecret in a mobile app, in browser code, or in an environment variable that reaches the browser (such as NEXT_PUBLIC_… in Next.js).

Responses

The API uses standard HTTP status codes: 200 or 201 on success, 4xx when the request can't be done, 5xx when something went wrong at IDfier. The body is JSON with a numeric status and data:

{
  "status": 100,
  "data": { "referenceId": "550e8400-e29b-41d4-a716-446655440000" }
}

Errors carry the reason in data.error:

{
  "status": 101,
  "data": { "error": "Session not found" }
}

Branch on the HTTP status; see Errors for every code.

Make a first call

curl -X POST https://api.idfier.com/api/v3/business/auth/request \
  -H "clientid: $IDFIER_CLIENT_ID" \
  -H "clientsecret: $IDFIER_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{}'

A 201 with a referenceId means your credentials work.

Testing

There is no sandbox yet: testing uses the production API, the IDfier app and a real, verified IDfier profile (your own). Ask IDfier for a separate business client for testing.

Next

On this page