paytrack docs
Authentication
Authenticate paytrack API requests with scoped bearer tokens created from your workspace.
API keys
Every API request must include an API key in the Authorization header. Keys belong to a workspace, user, plan, mode, and set of scopes.
Example
Authorization: Bearer ptrk_test_xxx Authorization: Bearer ptrk_live_xxx
Test keys and live keys
Test keys use the ptrk_test_ prefix and are safe for development workflows. Live keys use ptrk_live_ and should only run from trusted server environments.
One-time display
paytrack only shows a raw API key once. After that, only the prefix and last four characters are visible because the server stores a hash, not the raw secret.
Authorization failures
Revoked, expired, malformed, or missing keys return 401 Unauthorized. Valid keys without the needed scope or subscription access return 403 Forbidden.
Example
{
"success": false,
"error": {
"code": "invalid_api_key",
"message": "The provided API key is invalid or has been revoked.",
"details": {}
},
"request_id": "req_xxx"
}Subscription access
Plans control API availability, monthly request quota, rate limits, available scopes, webhook access, report access, and reminder access.