Skip to main content
POST
Dry-run the saved OAuth 2.0 client-credentials config

Authorizations

Authorization
string
header
required

Bearer token in the Authorization header. Two token types are accepted:

  • Organization API key (sk_...) issued via the dashboard. Org-scoped, long-lived, for server-to-server use.
  • User JWT obtained via the OAuth 2.1 authorization code flow with PKCE. User-scoped, short-lived. Discover the authorization server at /.well-known/oauth-authorization-server and the protected-resource metadata at /.well-known/oauth-protected-resource/api.

Path Parameters

encodedUrl
string
required

URL-encoded agent URL

Response

Result of the token exchange. ok: true on 2xx from the AS; ok: false with a typed error otherwise (HTTP response itself is still 200 — the error payload carries the rejection kind so UI can branch on it).

ok
enum<boolean>
required
Available options:
true
latency_ms
integer
required