Developers

An open property management API, yours to build on.

Zrico's property management API is a versioned REST API under /v1, with keys scoped per area, an OpenAPI 3.1 document generated from the same definitions the API checks, and signed webhooks for events. Anything with money, sending, deleting or legal effect that a key asks for waits for a person to approve it in the app.

Built for programs on a server: an accounting sync, your website, a spreadsheet you script.

Updated November 17, 2026

What can the API do?

Read properties, units, listings and owners. Read and write tenants, vendors, work orders, charges and payments. Subscribe to events with webhooks, and run any action Zrico can do through the actions endpoint.

  • Lists are newest first, a page at a time, with a cursor.
  • Creates accept an Idempotency-Key, so a retried request never makes a second payment.
  • Every error has the same shape: a code, a message, any field issues and a request id.

How do API keys work?

An admin makes each key in Settings, gives it a name and chooses its access: read, or read and write, per area. The key is shown once; only a hash is stored.

  • Each key has its own requests-per-minute limit.
  • Revoking a key stops it at once.
  • Changes made with a key show in the audit log as the key's person, through the API.
  • There are no CORS headers, so a key can't be used from a web page in someone's browser.

Where are the docs?

The OpenAPI 3.1 document is generated from the endpoint list and its schemas, so the docs can't drift from what the API accepts and returns. An interactive API reference, served from Zrico itself, lets you try requests.

How do webhooks work?

Add an address and pick the events it should get, like a payment coming in or a repair being asked for. Each event is sent as a signed POST carrying ids and amounts only; your program reads the rest through the API.

  • Signed as the Standard Webhooks spec describes, with an HMAC-SHA256 signature, so its open-source libraries can verify them.
  • Failed sends are retried with longer waits for about a day and a half.
  • The last 20 events sent are shown in Settings and kept for 30 days.

What happens when the API asks for something risky?

The actions endpoint runs an action as the key's person, with their permissions. A look-up or small change is done at once. Anything with money, sending, deleting, legal effect or access waits for a person to approve it in Zrico approvals, and the API answers with the approval's id.

FAQ

Questions, answered.

Still have a question? Ask our team

Does Zrico have an API?

Yes. A versioned REST API under /v1 with scoped keys, OpenAPI 3.1 docs and signed webhooks.

Who can create API keys?

Admins, in Settings. Give each program its own key, so one can be revoked without stopping the others.

Can the API move money without approval?

Recording a payment or charge through its endpoint is limited by the key's scope and its person's permissions. Through the actions endpoint, anything with money, sending, deleting or legal effect waits for a person to approve it.

How do I verify a webhook?

Check the webhook-signature header, an HMAC-SHA256 of the event id, timestamp and body with your signing secret, as the Standard Webhooks spec describes. The secret is shown once, when you add the webhook.

Is there a rate limit?

Yes. Each key has its own requests-per-minute limit, set when the key is made. Over it, the API answers with a request to wait.

See Zrico run your portfolio.

Bring a property. We will show you, on your own data, what Zrico would have handled last month.