Authentication (1.0)

Exchange a client_id and client_secret for a Bearer access token.

One credential set covers both APIs. The same OAuth2 client credentials, and the same Quiqdash Bearer key, authenticate against the Fulfilment host and the Last-mile host. There is no separate fulfilment credential to request.

Most integrations do not need the exchange at all. A Bearer token generated in Quiqdash under Organization -> API keys grants identical access with no token endpoint involved. Client credentials exist for middleware and carrier platforms whose setup screens require a Client ID and Client Secret.