Skip to main content
POST
Register a client
Most integrations never call this. An MCP client that supports OAuth sign-in calls it on its own when you add PostQueen by its sign-in address. Call it yourself only when you build a client that registers itself (Dynamic Client Registration, RFC 7591). The answer carries a pcd_ client id. A public client (token_endpoint_auth_method: none) gets no secret, so it must use PKCE with S256 on the consent URL and send the code_verifier in the token exchange. The other steps are the same as for an app made under Connections > Developers; see OAuth apps.

Body

application/json
redirect_uris
string[]
required

The callback URLs the client may use

Minimum array length: 1
client_name
string

The name shown on the consent screen, up to 100 characters. Default MCP Client

client_uri
string

Accepted and not stored

logo_uri
string

Accepted and not stored

token_endpoint_auth_method
enum<string>

none for a public client with PKCE. Anything else gets a secret; the default is client_secret_post

Available options:
none,
client_secret_post,
client_secret_basic
grant_types
string[]

Must include authorization_code when sent

response_types
string[]

Accepted; the answer is always code

scope
string

Accepted; the scope is set by PostQueen

Response

Registered. client_secret is present only for a confidential client, and is shown once

client_id
string
client_secret
string
client_secret_expires_at
integer

0: the secret does not expire

client_id_issued_at
integer

Unix time in seconds

client_name
string
redirect_uris
string[]
token_endpoint_auth_method
string
grant_types
string[]
response_types
string[]
scope
string
Last modified on September 23, 2026