Request Token (OAuth Format)

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Use the OAuth-style authentication endpoint when you want the same credentials expressed in an OAuth client_credentials-style request:

  • The request uses Client_ID and Client_Secret with grant_type=client_credentials.
  • Your integration already works with client_id/client_secret inputs and prefers a combined identity string (Account:Client:ApiUser).
  • You want to avoid handling discrete Account/User/Password fields in the client.
  • Your platform, proxy, or tooling expects OAuth-like request fields for consistency across services.
  • You need clearer audit attribution to a client_id string in your own logs and dashboards.
  • You are building automated or headless server-to-server jobs where an interactive login flow is not required.

Not ideal when:

  • Your environment or scripts are simpler with discrete JSON fields (Account, User, Password, ClientName).
  • Your existing tooling, tests, or monitors are built around the simple login-style input format and you want to minimize changes.
Body Params
string
required
Defaults to client_credentials

"client_credentials" is the only OAuth Grant_Type that Origami's APIs support.

string
required

This is a composite value composed of: "{AccountName}:{ClientName}:{UserName}". Ex: Client_ID: "Account:Client:ApiUser"

string
required

This is password of the API User named in the Client_ID

Responses

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json