Flavours Partner API

Authentication

How to authenticate your requests to the Flavours API.

Every request to the Flavours API must be authenticated. Your API key identifies your integration, so keep it secret — anyone who has it can make requests on your behalf.

Get your API key

Use the API key provisioned for your integration. If you don't have one yet, contact your Flavours account manager.

Send it with every request

Include the following header on each request to the API:

API-TOKEN: <your-key>

Or set it once in the playground

Save your API key here — or from the Authorize button in the header — and it is reused across every endpoint’s Try it panel, so you only enter it once. It is stored in your browser.

Authorize the playground
Save your token once here and it is reused across every “Try it” request. It stays in this browser only.
Not set

Sent as the API-TOKEN header on every request.

Keep your API key secret

Never commit your API key to source control or expose it in client-side code. If it leaks, revoke it and issue a new one right away.

Connecting a third-party system?

Systems that authenticate with a client ID and secret use a separate credential, an integration access token. See Integrations.

Introduction

What the Flavours API is, its base URL and environments, and how to read this reference.

Overview

What a Flavours integration is, how a system authenticates with client credentials, and what an access token can call today.