API Authentication - EmailBison Docs

API Keys

EmailBison uses to authenticate requests. You can create tokens by visiting Settings -> Developer API -> New API Token. There are two types of tokens (keys) you can create.

api-user tokens only authenticate for the workspace they were created in. Each workspace will need a separate token.
super-admin tokens impersonate the user that created them. While they can only be scoped to one workspace at a time, the workspace they are scoped to will change if the user changes their workspace.

It is recommended to use api-user keys. They are simpler to manage, and generally offer the same permissions.

Authorization

All API requests should include your API key in an Authorization HTTP header as follows: Authorization: Bearer YOUR_API_KEY Where Authorization is the Key in your header, and Bearer YOUR_API_KEY is the Value. An example of a request that is properly authenticated:

curl https://dedi.emailbison.com/api/users \
  --header 'Authorization: Bearer 9|q8kSmhjJRqJVT2kc1M0ezX640Pxk'

fetch('https://dedi.emailbison.com/api/users', {
  headers: {
    Authorization: 'Bearer 9|q8kSmhjJRqJVT2kc1M0ezX640Pxk'
  }
})

url = "https://dedi.emailbison.com/api/users"

headers = {"Authorization": "Bearer 9|q8kSmhjJRqJVT2kc1M0ezX640P"}

response = requests.get(url, headers=headers)

⌘I