When you call a Stedi endpoint, you need to provide an API key in the Authorization-header. API Keys lets you create and delete these keys programatically.
An API Key grants access to all resources belonging to a tenant. If you sign up with Stedi as an individual, then you are the tenant and all resources belong to you alone. If you are a member of an account, then the account is the tenant and all resources are shared among the account's members.
Maximum number of API keys that will be returned in a single response. If there are more API keys, the response will contain a field
next_page_token that will allow you to retrieve them.
A token that allows you to retrieve the next page of API keys. It should have the same value as the
next_page_token-field you received in your last response.
Create a new API key for the active tenant. The active tenant is determined by the API key passed in the Authorization-header.
When you call a Stedi endpoint, you need to provide an API key in the Authorization-header. Any API key you create using this endpoint grants you access to all resources belonging to the active tenant. If you signed up as an individual, then the active tenant is you and the API key will grant access to all your resources. If you're a member of an account, then the active tenant is the account and the API key will grant access to all resources in that account, regardless of whether they were created by you or by another member.
Since you need an API key to call this endpoint, you need to create your first API key using the UI.