Bynder Developer Platform

Start building with Bynder

Authenticate once with OAuth 2.0 and build across 170+ REST endpoints — assets, upload, delivery, workflow and governance.

Four ways to build


Authenticate with OAuth 2.0

Bynder uses OAuth 2.0 for all API access. Register an OAuth client application in your Bynder portal settings to obtain a client ID and client secret. Three grant types are supported:

authorization_code

User-facing apps where a real user logs in and grants access. Recommended for integrations that act on behalf of a user.

client_credentials

Server-to-server or automated workflows. No user interaction required — exchange credentials directly for a token.

refresh_token

Exchange a refresh token for a new access token without requiring the user to re-authorize.

Example — see the OAuth 2.0 reference for exact parameters and scopes.

curl -X POST "https://{portal-domain}.bynder.com/v6/authentication/oauth2/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  --data-urlencode "grant_type=client_credentials" \
  --data-urlencode "client_id={client_id}" \
  --data-urlencode "client_secret={client_secret}" \
  --data-urlencode "scope={scope}"
OAuth 2.0 reference →

Your first call

1 · Create an app

Register an OAuth2 client in your Bynder portal settings to get a client ID and secret.

2 · Get a token

Exchange your credentials for a bearer token.

POST /v6/authentication/oauth2/token

3 · List assets

Pass your bearer token in the Authorization header and confirm your setup end-to-end.

GET /api/v4/media