Skip to content
Developers

Getting started

Environments

On this page

Bizisy has one environment: production, at https://api.bizisy.com. There is no sandbox host and there are no test keys: every key belongs to a real company, and every committed call changes that company's data.

Try changes safely with dry runs#

Add ?dry_run=true to any write. Bizisy runs every check (permissions, validation, approvals, conflicts) and answers with what would happen, then saves nothing and sends nothing: no email, no webhook, no Activity entry. Use it while you build, and in production before every change you aren't sure about (Dry runs).

Shell
curl "https://api.bizisy.com/v1/org/people.hire?dry_run=true" \
  -H "Authorization: Bearer $BIZISY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"given_name":"Bea","family_name":"Santos","work_email":"bea@acme.com","title":"Designer","start_date":"2026-11-02"}'

A company for testing#

If you want somewhere to experiment with real writes, create a second company at bizisy.com/signup. It is an ordinary company: billed the same way as any other (see Pricing), with its own address, people and keys. Close it from Settings → Close account when you're done.

Versions#

There is one API version, /v1. Changes are additive: new actions, new optional input fields and new output fields. Write clients that ignore fields they don't know, and follow the changelog.

Limits that apply everywhere#

  • Rate limits: 300 requests per minute per key.
  • Request bodies up to 2 MiB (photo and logo uploads: 3 MiB).
  • HTTPS only. Plain http:// to the API host is refused, so a key is never sent in clear text.

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

Developer docs