Skip to content

Build an app

Access tokens

On this page

An access token lets your own scripts, CI jobs and AI assistants work with your apps without your browser: the same actions as the developer console, with the same checks. Tokens start with bzd_ and belong to your developer account, never to a company.

They work only on the developer site:

  • the console's REST API, https://developers.bizisy.com/api/v1/developers/… (its OpenAPI is at https://developers.bizisy.com/api/v1/openapi.json), and
  • the developer MCP server, https://developers.bizisy.com/mcp (Build with an AI assistant).

A company address and https://api.bizisy.com refuse them, and the developer site refuses a company's API keys, app tokens and connected-app tokens.

Create one#

In the console, open Account → Access tokens → Create a token (it needs a sign-in from the last 15 minutes, so a stolen browser session can't make one):

NameWhat it is for, such as "Claude on my laptop". Activity shows it: "via token Claude on my laptop".
Scopesapps:read (read your apps, their versions and your organizations) and/or apps:write (also create and change apps, upload images, submit and withdraw). apps:write includes apps:read.
OwnerEvery owner you work for, or one: yourself or one organization. A token limited to one owner can't see or change any other owner's apps.
ExpiresAfter 90 days by default, at most 365.

The token is shown once: copy it and store it like a password. Bizisy keeps only a fingerprint (a hash) of it, so a lost token can't be shown again: revoke it and create a new one. You can have at most 20 active tokens.

Revoke stops a token at once. Expired and revoked tokens stay listed for 30 days, then disappear. Deleting your developer account deletes your tokens; while Bizisy suspends an account, its tokens are refused.

Use it#

Send it as a bearer token:

Shell
curl https://developers.bizisy.com/api/v1/developers/apps.list \
  -H "Authorization: Bearer bzd_…" \
  -H "content-type: application/json" \
  -d '{}'

A request with an Authorization header is judged by its token alone: the console's sign-in cookie is never used with it. Each token may make 300 requests a minute; writes take dry runs and idempotency keys like any client. Your role in each organization still applies: a token never does more than you could in the console.

What a token can do#

ScopeActions
apps:readdevelopers.me.get, developers.apps.list, developers.apps.get, developers.apps.versions.list, developers.apps.manifest.validate, developers.organizations.list, developers.organizations.get, developers.sandbox.get (and the public directory reads)
apps:writedevelopers.apps.create, developers.apps.update, developers.apps.setup.create, developers.apps.setup.save, developers.apps.image.upload, developers.apps.image.remove, developers.apps.submit, developers.apps.withdraw, developers.apps.webhook.test
Console only (refused for every token)Access tokens, client secrets (developers.apps.secret.rotate), deleting and transferring apps, creating, changing, deleting and leaving organizations, their logos, members and roles, invitations, the sandbox (create, delete, open, address check), your account (change, delete, download your data), your Activity, the companies where you can test, and signing up

A token can never install an app: installing always needs a person on a company's consent screen in a browser (Install with OAuth).

Something missing or wrong on this page? Write to hello@bizisy.com.

Developer docs