Skip to main content
📌 Note: These endpoints require an active subscription. They are how customers obtain the application token used to authenticate all data APIs.
The typical flow is: log in to obtain a user id_token, call /api/application/create to create an application (which returns a client_id and client_secret), then call /api/application/generate-token with those credentials to mint an application token (app_token). Use that app_token as the Bearer token for the data APIs. All endpoints below are authenticated with either a user id_token or an application app_token, and require an active subscription. Successful responses are wrapped in the standard { "meta": ..., "data": ... } envelope.

POST /api/application/create

Create a new application for your company. Returns the client_id and client_secret used to generate tokens. The number of applications you may create is limited by your subscription tier.

Authorization

🔒OAuth2: OAuth2PasswordBearer
Flow type: password
Token URL: token

Request Body

The request body must be in application/json format.

Request Example

Responses

  • 200: Successful Response
  • 422: Validation Error

POST /api/application/generate-token

Use an application’s client_id and client_secret to generate a temporary application token (app_token). This token is the Bearer token used to call the data APIs. The number of valid tokens per application and the token validity period are determined by your subscription tier (default validity is 90 days).

Authorization

🔒OAuth2: OAuth2PasswordBearer
Flow type: password
Token URL: token

Request Body

The request body must be in application/json format.

Request Example

Responses

  • 200: Successful Response
  • 422: Validation Error

GET /api/application/token-info

Get information about the application token used to authenticate the request. Call this endpoint using the app_token as the Bearer token.

Authorization

🔒OAuth2: OAuth2PasswordBearer
Flow type: password
Token URL: token

Responses

  • 200: Successful Response

POST /api/application/update

Update an application’s name or description. The client_id and client_secret cannot be modified after creation.

Authorization

🔒OAuth2: OAuth2PasswordBearer
Flow type: password
Token URL: token

Request Body

The request body must be in application/json format.

Request Example

Responses

  • 200: Successful Response
  • 422: Validation Error

POST /api/application/info

Get detailed information about a single application, including its tokens. Provide at least one of id or name.

Authorization

🔒OAuth2: OAuth2PasswordBearer
Flow type: password
Token URL: token

Request Body

The request body must be in application/json format. * At least one of id or name must be provided.

Request Example

Responses

  • 200: Successful Response
  • 422: Validation Error

POST /api/application/list

List your applications and their tokens. Customers see only their own company’s applications. An optional search body can be supplied for filtering, ordering, and pagination.

Authorization

🔒OAuth2: OAuth2PasswordBearer
Flow type: password
Token URL: token

Request Body

The request body must be in application/json format. All fields are optional; send an empty object {} to list all of your applications.

Request Example

Responses

  • 200: Successful Response

DELETE /api/application/delete

Delete an application by id or name. All valid (non-expired) tokens for the application must be removed first. Provide at least one of id or name.

Authorization

🔒OAuth2: OAuth2PasswordBearer
Flow type: password
Token URL: token

Request Body

The request body must be in application/json format. * At least one of id or name must be provided.

Request Example

Responses

  • 200: Successful Response
  • 422: Validation Error