Skip to content

Build an app

Build a Bizisy app

On this page

A Bizisy app is your service, connected to the companies that install it. A company finds it in Integrations → Browse (and in the app directory), an owner or admin presses Install, checks what your app may do in plain words, and allows it. Your app then works with that company's data through the same REST API, MCP servers and webhooks as everyone else, acting as the app, not as a person.

Anyone can build one, with a free developer account on developers.bizisy.com. Developer accounts are never billed.

How it fits together#

  1. Create a developer account (sign up with an email, Google or Microsoft). Your apps can be your own, or belong to an organization you build with other developers.
  2. Create the app in the console's studio (My apps → Create an app). Start from a template (people directory sync, chat notifier, payroll export, IT onboarding), a blank app, or Paste a manifest. The studio is one page: Name & look (name, one line, logo and accent colour, address), What it does (what the app may do, in plain words; each choice asks for the matching scopes and webhook events, and Advanced lists them raw), Connect (redirect URLs with a Test, the webhook URL with Send test event, and code for your server) and Listing. Beside it, a live preview shows your directory card, your listing page and the consent screen companies will see, as you type; above it, what is still missing to install the app in your company and to submit it for review. The app is saved as a private draft when you continue past Name & look, and as you go after that; Manifest shows the same manifest as JSON, edited both ways.
  3. Create the draft and install it in your company: Create draft & install in (when you are an owner or admin of a Bizisy company), or Create draft and install it later in a company where you are an owner or admin (or ask one to link your organization to their company: its owners and admins can then install your draft). Create a client secret (the app → Credentials; it is shown once), install it from the company's Integrations, and follow the OAuth flow. Until Bizisy approves a version, your app is private: only test installs use its draft.
  4. Submit it for review. Bizisy's team checks it against the review guidelines and approves it or tells you what to change. Approved, it is listed for every company, which install it through OAuth: you get tokens for their install, a webhook signing secret, and you start working.

An app only your own company needs can be private: no review, never listed. You can also build with an AI assistant: an access token and the developer MCP server.

Where a draft can be installed#

An app's draft manifest (what you are editing) is an unreviewed draft. It installs only in:

  • a company where you are an owner or admin, if you can work on the app (yours, or an organization's you belong to): the same person as your developer account, signed in to that company. Only you can install it there, on the company's normal consent screen, which says it is an unreviewed draft. Its Integrations page then shows "Unreviewed draft", and its Activity records the install. The company can uninstall it at any time;
  • for an organization linked to a company, that company.

Every other company installs the version Bizisy approved. http://localhost redirect and install URLs work only for these test installs.

A draft you installed in your company keeps working if you later stop being an owner or admin there (the company decides whether to keep it), but no new draft can be installed or re-consented there. It stops working (its tokens and its webhooks) if you leave the company, or can no longer work on the app: you left its organization, it was transferred to an owner you don't belong to, or your developer account was suspended or deleted. A company that runs the reviewed version of your app never gets your draft instead: test new drafts elsewhere.

What an install is#

Who it acts asThe app, in one company (Activity shows your app's name)
What it can doThe scopes the company consented to, plus what every employee can read (the company directory)
Private details and payNever, unless it has the special scope private:read or pay:read and the company ticked the box
Where tokens workhttps://api.bizisy.com/v1 and https://api.bizisy.com/mcp/manage, or the company's own address
Limits300 requests a minute per install, dry runs and idempotency keys like any client
Ends whenThe company uninstalls it, Bizisy suspends the app or its owner, or you delete the app

Bizisy charges companies nothing for installing apps; if your service is paid, link your own pricing page from the manifest.

The console's API#

Everything in the console is an action too, under https://developers.bizisy.com/api/v1/developers/… (its OpenAPI is at https://developers.bizisy.com/api/v1/openapi.json). It works with the console's sign-in or with an access token (bzd_…); a company's API keys never work there.

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

Developer docs