We’re making some important changes to the JustGiving APIs as part of our move to the Blackbaud SKY API platform.

These changes include new API endpoints and a move to OAuth 2.0 for authorisation.

If you maintain an application or integration using the JustGiving APIs, you'll need to update your integration to support these changes.

JustGiving uses the same OAuth 2.0 Authorization Code Flow as SKY API.

If you're already familiar with the SKY API authorisation process, the main differences for JustGiving are the authorisation endpoint and a small number of JustGiving-specific parameters.

For a complete overview of the standard authorisation flow, token handling, refresh tokens, PKCE and security best practices, please refer to the SKY API Authorisation Documentation. SKY API Authorization Documentation

The SKY API documentation also strongly encourages the use of PKCE and the state parameter when using the Authorization Code Flow.

Authorisation endpoint

Unlike standard SKY API applications, JustGiving applications should direct users to the JustGiving authorisation endpoint:

https://app.justgiving.com/oauth/authorize

The token endpoint remains the standard SKY API token endpoint:

https://oauth2.sky.blackbaud.com/token

The latter is the documented SKY API token endpoint.

The JustGiving authorisation request supports the standard SKY API OAuth parameters used within the authorisation flow, alongside the JustGiving-specific parameters detailed below.

Your request may therefore include:

client_id

redirect_uri

response_type=code

scope

state

code_challenge

code_challenge_method

Your redirect_uri must exactly match one of the redirect URIs configured for your application, including any trailing slash.

JustGiving parameter: svv

svv must be set to jg to identify the authorisation flow as a JustGiving branded experience.

e.g. svv=jg

Optional charity branding

JustGiving also supports an optional parameter for applying charity-specific branding to the login and consent experience.

envid specifies the charity branding environment. When supplied, the authorisation experience displays the configured charity branding. When omitted, the standard JustGiving branding is shown. To identify the envid reach out to developer@justgiving.com.

Standard SKY API

• https://app.blackbaud.com/oauth/authorize
• No svv parameter
• Supports environment_id for environment targeting
• Standard Blackbaud authorisation experience

JustGiving SKY API

• https://app.justgiving.com/oauth/authorize
• svv=jg required
• Optional envid for JustGiving charity branding
• JustGiving authorisation experience

The standard SKY API authorisation URL is https://app.blackbaud.com/oauth/authorize, and SKY API supports the optional environment_id parameter for targeting a specific environment. The experience will be Blackbaud branded on standard SKY API implementations.

To prepare for the changes to the JustGiving APIs:

• Prepare to update your API endpoints once the new endpoints are published.
• Implement the OAuth 2.0 Authorization Code Flow for JustGiving.
• Use the JustGiving authorisation endpoint: https://app.justgiving.com/oauth/authorize
• Include svv=jg in the JustGiving authorisation request.
• Continue to use the standard SKY token endpoint: https://oauth2.sky.blackbaud.com/token
• Use PKCE and state in line with SKY API security guidance.
• Support the optional envid parameter where charity-specific branding is required.

Ensure your configured redirect_uri exactly matches the value used in your authorisation request.

JustGiving is moving to new API endpoints and OAuth 2.0 authorisation.

Developers should plan to update their integrations to use the new endpoints and the JustGiving OAuth 2.0 authorisation flow described above.