The Sourcengine API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request and response bodies, and uses standard HTTP response codes, authentication, and verbs.

To give you an idea of how to use our API, we have annotated the documentation with code samples written in popular programming languages. Use the language selector at the top right to switch between them.

Sourcengine API uses API tokens to allow access to the API. You can consult with your account manager to get a valid token in order to sign your requests. Your API token carries many privileges, so be sure to keep them in a secure vault. Do not share your secret API keys in a publicly accessible area such as GitHub or client-side code.

The token is expected to be included in all API requests to the server, inside a header that looks like the following:

Authorization: Bearer {access-token}

Example signed request:

curl -H "Authorization: Bearer {access-token}"