Send an MCP message (dealer URL)
POST/dealers/:dealer/mcp
The same server as /mcp, at the URL the DMS gives a dealer to paste
into an AI assistant. When the assistant signs in with OAuth it sends
this URL as resource, so /oauth/authorize takes the dealer
straight to the consent screen in their own DMS rather than asking
them to sign in centrally first. A token for another dealer is
refused with 403 wrong_dealer.
Request
Responses
- 200
- 202
- 401
- 403
- 429
A JSON-RPC 2.0 response, as for /mcp.
A notification was received. No body.
No key, or one that cannot be used. Codes: missing_api_key,
invalid_api_key, api_key_revoked, api_key_expired,
key_owner_inactive.
Response Headers
This request's id. Quote it to support.
Bearer.
The key may not do this. Codes: insufficient_scope,
scope_not_permitted_for_owner, plan_not_entitled,
secret_key_required, publishable_key_required,
secret_key_in_browser, origin_not_allowed, ip_not_allowed,
branch_move_not_permitted, plan_stock_cap_reached,
sandbox_stock_cap_reached, not_available_in_sandbox,
theme_builder_not_enabled, agency_key_required,
agency_not_approved, agency_access_revoked.
Response Headers
This request's id. Quote it to support.
Too many requests. Code rate_limited; wait Retry-After seconds. On POST /theme-generations, also theme_generation_quota_exceeded, when the dealer's monthly theme generations are used up (no Retry-After).
Response Headers
This request's id. Quote it to support.
Requests allowed per minute for this key.
Requests left in the current minute.
Seconds to wait before retrying.