Register an OAuth client
OAuth 2.1 Dynamic Client Registration (RFC 7591). Registration is authenticated: the caller must present a valid HQ session or token, and the resulting client is owned by that user. Validates the submitted JSON metadata (redirect URIs must be https or http loopback with no fragment; scopes must be known capability scopes; token_endpoint_auth_method none yields a public client, client_secret_post/basic a confidential one). Returns 201 with the new client_id, a registration_access_token, and, for confidential clients, a client_secret (the secret and registration token are shown only once), plus a registration_client_uri for managing the client. Registered clients are always treated as third-party and shown the consent screen, and each account is capped on how many it may register.
Dynamic client registration (RFC 7591)
Registers a new OAuth client and returns itsclient_id and registration metadata. Public clients (e.g. browser apps) use PKCE and have no secret. Provide your redirect_uris and the scopes the client may request. Afterwards, manage the registration with Get / Update / Delete using the returned credentials.Authorizations
Personal Access Token. Send as Authorization: Bearer hq_pat_....
Body
Response
Registered client (client_id + one-time secret/registration token), RFC 7591