Official documentation for authenticating with our API
Authorization
header of all subsequent requests.
Token Rotation: We recommend periodically rotating tokens and storing them securely.
Method: POST Format: JSON
Parameter | Required | Fixed Value | Description |
---|---|---|---|
grant_type | Yes | password | Indicates that you’re using authentication via email and password. |
Key | Value | Description |
---|---|---|
Content-Type | application/json | Indicates that the request body is in JSON format. |
access_token
— you’ll use it to interact with the rest of the API.
Method: POST Format: JSON
Parameter | Example | Required | Description |
---|---|---|---|
Authorization | Bearer your-access-token | Yes | This header is used for authenticating the request. It contains a Bearer token received after logging in. |
validApiKeys
array represents an API key associated with a specific company. The fields included are:
company_id
: Unique identifier of the company that owns the API key.
key
: The API key itself, used to authenticate requests.
is_active
: Boolean value indicating whether the key is currently active (true) or inactive (false).
last_used
: Timestamp of the last time the key was used. If the key has never been used, the value will be null.
company_name
: Name of the company associated with the API key, useful for display in interfaces or logs.
key
provided in the response to authenticate future requests and perform operations on behalf of the specified company.
📝Each company will have a unique access key. You must use the correct key depending on which company you’re interacting with.
key
in your query parameters or headers, depending on the endpoint.