FIRST_PARTY_CLIENT_REQUIRED

Only Ticketlayer's own apps may do this

HTTP status 403 Forbidden, code FIRST_PARTY_CLIENT_REQUIRED.

What it means#

The sign-in steps under /auth (start, password, email-code, mfa) are for Ticketlayer's own apps, and the client_id named is not one of them. Or a person's connected apps (/me/grants) were asked for with an access token a third-party app holds for the person: an app may not list or revoke the person's other apps.

What to do#

To sign a person in from a third-party app, use the authorization code flow with PKCE: send the person to the issuer's /oauth/authorize, as its discovery document describes. A person manages their connected apps in Ticketlayer's own apps (Manage), signed in as themselves.

On the wire#

Every error response carrying this code names this page in error.moreInfo, with the request id in the query string. See Error codes for the response shape and the list of every code.