Mint a connect link for an MCP application's upstream accounts
Returns a connect ticket an admin can open to link the application’s own accounts on the servers that forward a stored credential — the same page the api-key self-service flow uses, without needing one of the application’s credentials. Naming a registry narrows the ticket to that one server; omitting it covers every server of the application that forwards a credential. The ticket is pinned to this consumer and to those providers, revalidated on redemption, audited, and short-lived.
POST
/
v1
/
gateways
/
{gateway_id}
/
consumers
/
{id}
/
upstream-accounts
/
link
Error
A valid request URL is required to generate request examples{
"connect_path": "<string>",
"consumer_path": "<string>",
"expires_at": "<string>",
"providers": [
"<string>"
],
"ticket": "<string>"
}{
"error": "<string>",
"message": "<string>"
}{
"error": "<string>",
"message": "<string>"
}{
"error": "<string>",
"message": "<string>"
}{
"error": "<string>",
"message": "<string>"
}Authorizations
Query Parameters
Authorize only this bound MCP server
⌘I
Error
A valid request URL is required to generate request examples{
"connect_path": "<string>",
"consumer_path": "<string>",
"expires_at": "<string>",
"providers": [
"<string>"
],
"ticket": "<string>"
}{
"error": "<string>",
"message": "<string>"
}{
"error": "<string>",
"message": "<string>"
}{
"error": "<string>",
"message": "<string>"
}{
"error": "<string>",
"message": "<string>"
}