Authentication
How to authenticate with the Graphite Connect Public API using OAuth 2.0
Authentication
The Graphite Connect Public API uses OAuth 2.0 client credentials flow. All API traffic must be sent over HTTPS (port 443) using TLS 1.2 or higher.
Getting Your API Key
To obtain an API key, contact [email protected]. Your API key serves as both your OAuth client ID and client secret.
Obtaining a Bearer Token
Exchange your API key for a bearer token by calling the token endpoint:
curl -X POST https://app.graphiteconnect.com/api/oauth/token \
-H "Content-Type: application/json" \
-d '{
"grant_type": "client_credentials",
"client_id": "YOUR_API_KEY",
"client_secret": "YOUR_API_KEY"
}'The response will contain an access_token:
{
"access_token": "eyJ...",
"token_type": "Bearer",
"expires_in": 3600
}Using the Bearer Token
Include the bearer token in the Authorization header of all subsequent API requests:
curl -X GET https://app.graphiteconnect.com/api/public/api/v1/changes/connections \
-H "Authorization: Bearer eyJ..."Security Requirements
- All requests must use HTTPS on port 443
- Minimum TLS version: TLS 1.2
- Tokens expire — re-authenticate using the same flow when needed
Interactive Testing
You can test API calls directly in the browser using the Swagger UI:
URL: https://app.graphiteconnect.com/api/public/api/v1/documentation/#
- Click Authorize in the top-right corner
- Enter your bearer token
- Use Try it out on any endpoint to make live API calls
Updated about 7 hours ago
