Skip to main content
Workspace API keys let a server-side integration use the public Biqli API. Create a key from developer settings, give it a name that identifies the application and environment, and choose the smallest permission set it needs. Copy the secret when Biqli displays it. The full value is shown once and cannot be recovered later. Store it in a secret manager or protected environment variable, never in browser code or source control. The key is scoped to the workspace where it was created. Its last-used information helps identify active and abandoned integrations.

​
Create a key

  1. Switch to the workspace the integration should control.
  2. Open developer settings and select API keys.
  3. Give the key a name containing the application and environment.
  4. Choose All, Read Only, or Restricted permissions.
  5. Create the key and copy its biqli_ secret immediately.
  6. Store it in the integration’s secret manager.
The full secret is displayed once. Biqli stores the protected credential needed to authenticate future requests and cannot show you the original value again.

​
Use the key

Send it in the HTTPS Authorization: Bearer header. Do not put it in query strings, browser JavaScript, mobile bundles, screenshots, or logs. Use a separate key for production, staging, and each independent vendor. Review last-used information and revoke keys that no longer have an owner or active integration.