NOTE: This documentation is currently in progress. We are providing it as a preview for those developers who have expressed interest in getting an early start.

SparqFest supports OAuth 2.0 for authorizing api requests. Your client will follow a standard OAuth 2.0 workflow to receive an access token from SparqFest. Each API request you make will, in turn, pass that token as part of an x-authorization header with the value Bearer <TOKEN>.

Other than the choice of header name, our OAuth support is pretty straightforward.

We are not an identity management service and our API should not be used to support identity management requirements.

Endpoints

We expose two core endpoints in support of the OAuth process:

• /api/v2/oauth/token
• /api/v2/oauth/revoke