Skip to main content

​
Get started

Prerequisites
  • Portal account — A registered account on the Developer Portal.
  • Local tools — A terminal with cURL, or an HTTP client such as Postman, to run the requests in this tutorial.
What you’ll learn By the end of this tutorial, you will have:
  • Opened a project in the Developer Portal and copied your Sandbox client ID and client secret
  • Exchanged them for an OAuth 2.0 bearer token using POST /token
1

Access your Developer Portal account

Sign in to the Developer Portal.
2

Open your project

In the sidebar, open Projects. Select an existing project, or use the next step to create one.
3

(Optional) Create a project

Create a project, choose the solution that matches your use case, name the project, then select Create Project.
4

Copy Sandbox credentials

Open the Credentials tab for your project. Copy the client ID and client secret you will use for Sandbox (uat). You will paste them into the token request in the next step.
5

Exchange credentials for a bearer token

Prove Platform APIs use OAuth 2.0 client credentials. Send a POST to the token endpoint with Content-Type: application/x-www-form-urlencoded and your values in place of the placeholders.
If you are testing outside North America, use the EU token host and the International credentials from your project: https://platform.uat.eu.proveapis.com/token.
curl -X POST https://platform.uat.proveapis.com/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials&client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET"
Example token response
{
  "access_token": "eyJ...",
  "refresh_token": "eyJ...",
  "refresh_expires_in": 3600,
  "token_type": "Bearer",
  "expires_in": 3600
}
Copy the access_token value. You will send it as a Bearer token on API calls.If a Platform request returns HTTP 403 Forbidden, double-check the URL, HTTP method, and Content-Type for that operation. A frequent mistake is treating the token URL like a versioned API path (for example adding /v3). See HTTP 403 on the errors reference page.

​
Next steps

Related topics

Prove Unified Authentication OverviewImplement ProveXIntegrate the Unified Authentication client SDKBuild Prove with LLMsServer-Side SDK Guide