Skip to content
ApiqDevelopers
API v1.64.0Open console
API referenceidentity

Sign in

POST/v1/auth/sign-in

One sign-in for every realm — {username, password, siteId?} → the account's realm and its session

Added in v1.14.0. One login page for Apiq staff (OPERATOR), customer users (TENANT) and supplier users (SUPPLIER): the platform finds the account by its email in the platform-wide login directory (one…Show moreAdded in v1.14.0. One login page for Apiq staff (OPERATOR), customer users (TENANT) and supplier users (SUPPLIER): the platform finds the account by its email in the platform-wide login directory (one email is one account on the whole platform) and runs that realm's own login, with the realm's own lockout, MFA and session rules. The realm routes (/v1/auth/login, /ops/v1/auth/login, /supplier/v1/auth/login) are unchanged. 200 is a session of the named realm: exactly one of tenantSession, operatorSession or supplierSession is present. 202 is a next step after the password was accepted: MFA (the challenge is completed at that realm's own mfa/verify route) or SITE_CHOICE, when a customer user belongs to more than one site and sent no siteId (repeat the call with one of the listed siteIds). An unknown email, a wrong password, a locked or disabled account and a siteId the user does not belong to are one and the same 401 details.reason LOGIN_FAILED, so the route cannot be used to learn which realm, if any, an email belongs to. Plain JSON, not an envelope. Rate-limited per client and per subject as the identity routes are.

Request body

  • usernamestringRequired
    The account's email (a customer user provisioned with a plain username signs in with it too)
  • passwordstring · passwordRequired
  • siteIdstringOptional
    Customer users only, and only after a 202 SITE_CHOICE: the site to sign in to.Show moreCustomer users only, and only after a 202 SITE_CHOICE: the site to sign in to. Omitted, a customer user with one site signs in to it. Ignored for staff and supplier users.

Responses

  • 200Signed in — the session of the realm named in `realm`SignInResult
  • 202The password was accepted; one more step — MFA or a site choiceSignInNextStep
  • 400VALIDATION or UNKNOWN_DOMAINApiErrorResponse
  • 401
    UNAUTHENTICATED — missing or expired token.Show moreUNAUTHENTICATED — missing or expired token. Declared on every operation because `security` is declared globally at the document root: every route is authenticated, so every route can answer 401.
    ApiErrorResponse
  • 405
    VALIDATION — the public edge serves GET, POST, PUT, PATCH and DELETE only; any other method is refused before the platform sees it (details.reason METHOD_NOT_ALLOWED, details.source edge).Show moreVALIDATION — the public edge serves GET, POST, PUT, PATCH and DELETE only; any other method is refused before the platform sees it (details.reason METHOD_NOT_ALLOWED, details.source edge). Not retryable as sent.
    ApiErrorResponse
  • 413
    VALIDATION — the request body is larger than the surface's limit.Show moreVALIDATION — the request body is larger than the surface's limit. Not retryable as sent: shrink the body. Declared on every operation that takes a request body. details carries exactly one key, maxBodyBytes (integer): the limit that applies to this surface, in bytes.
    ApiErrorResponse
  • 414
    VALIDATION — the request URI (path and query string) is longer than 8 KiB; the public edge refuses it before the platform sees it (details.reason URI_TOO_LONG, details.source edge).Show moreVALIDATION — the request URI (path and query string) is longer than 8 KiB; the public edge refuses it before the platform sees it (details.reason URI_TOO_LONG, details.source edge). Not retryable as sent: send long input in the body of a POST.
    ApiErrorResponse
  • 415
    VALIDATION — a request body that is not JSON (application/json or application/*+json; a form body only on the OAuth token routes).Show moreVALIDATION — a request body that is not JSON (application/json or application/*+json; a form body only on the OAuth token routes). The public edge refuses it before the platform sees it (details.reason UNSUPPORTED_MEDIA_TYPE, details.source edge). Not retryable as sent: send Content-Type application/json. Declared on every operation that takes a JSON request body.
    ApiErrorResponse
  • 429
    Counted in fixed windows (default 15 min).Show moreCounted in fixed windows (default 15 min). The signup, login, password and invite routes count every attempt per client address AND per subject (the email, the username + site, or the invite token). POST /v1/oauth/token is counted three ways, none of them on client_id alone, so knowing a client_id (which is not secret) never lets anyone spend its holder's budget: oauth-token counts every attempt per client address only; oauth-token-failure counts FAILED client authentications per client address and per (client address, client_id) pair; oauth-token-issued counts tokens issued per client_id only, and only a request whose secret, grant_type and scope all passed can spend it. details.reason says which limit tripped (CLIENT_RATE_LIMITED | SUBJECT_RATE_LIMITED) and details.action which count (signup | signup-verify | login | password-forgot | password-reset | invite-accept | oauth-token | oauth-token-failure | oauth-token-issued). Retry-After is whole seconds to the end of the window, and details.retryAfterMs mirrors it. The answer is the same whether or not the account or key exists, so the limit cannot be used to enumerate accounts, and nothing the caller sent is echoed. adds three counts per client address for the MCP grant routes: oauth-authorize (GET /v1/oauth/authorize, which may fetch a Client ID Metadata Document), oauth-register (POST /v1/oauth/register) and oauth-device (POST /v1/oauth/device_authorization), and one count per MCP grant, oauth-exchange-grant (the token exchange of POST /v1/oauth/token, counted per grant after the exchange client and the subject token verified, default 120 a minute), whose details.reason is EXCHANGE_RATE_LIMITED.
    ApiErrorResponse
  • 500INTERNAL — a bug, and traceId is the support handle.ApiErrorResponse

Errors you should handle

Branch on code and honour retryable — never on the HTTP status alone.

400VALIDATION
message.intent.checkOut must be after message.intent.checkIn
not retryable
400UNKNOWN_DOMAIN
Unknown domain 'HOTELS'. Did you mean HTL?
not retryable
401UNAUTHENTICATED
The bearer token is expired. Re-authenticate and retry.
not retryable
405VALIDATION
This method is not served.
not retryable
413VALIDATION
The request body is larger than this API accepts (262144 bytes).
not retryable
414VALIDATION
The request URI is longer than 8 KiB.
not retryable
415VALIDATION
Send application/json.
not retryable
429RATE_LIMITED
Too many requests of this kind for this address or account. Wait for the Retry-After interval before trying again.
retryable
500INTERNAL
An unexpected error occurred. Quote the traceId to support.
retryable