DestinationsRegister your own OAuth client

Register your own OAuth client

Run consents as your own Google OAuth client: your brand on the consent screen, your own Cloud-project quota (300 req/min and 100,000/day, which is otherwise SHARED by everyone on Mythic's client), and your own Google verification. The secret is encrypted at rest and never returned.

Add the returned redirect_uri to the client's Authorized redirect URIs and enable the Data Manager API on its Cloud project, or consent fails.

curl -X PUT "https://mythic-analytics.gulp.workers.dev/client/v1/destinations/oauth/client" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
  "client_id": "example_string",
  "client_secret": "example_string"
}'
{}
PUT
/client/v1/destinations/oauth/client
PUT
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Client key as bearer token. Use an agency key (Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.

Client key as bearer token. Use an agency key (Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.
Content-Typestring
Required

The media type of the request body

Options: application/json
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Client key as bearer token. Use an agency key (Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.

Responses

Stored