API & webhooks

A REST API and signed webhooks for each client account.

Keep a client's contacts and records in step with the other tools they use, and let those tools know when something happens in ManageIt. The API and webhooks come with the Business plan.

Read the reference

The REST API

What the API covers

Everything lives under /api/v1 and works the same way, with one bearer token and consistent paging. You can write to a client's CRM data freely. Anything involving money or sent documents is read-only or limited to a few actions, so an integration can't quietly change an invoice.

Endpoints

Which resources you can change

Contacts, records, tags and webhook endpoints are yours to create, update and delete. You can send or void documents, cancel bookings and delete form submissions, and everything else, from payments to automation runs, is there to read.

Tokens

Tokens limited to one client account

Each token belongs to one client's subaccount and only gets the permissions you give it. Set an expiry date and access ends when the project does.

Filtering and pages

Filtering contacts and records

Narrow contacts and records with one filters parameter. Filter on any field, custom fields included, or on tags, and stack as many conditions as you need.

Outgoing webhooks

Webhooks for 19 events

Events

Choose the events and the conditions

Pick from 19 events across contacts, documents, signatures, payments, forms, bookings and records. Add conditions so you only hear about what matters, like document.sent only when it's an invoice.

Signatures

Signed with HMAC-SHA256

Every delivery is signed with HMAC-SHA256 and timestamped, so your system can check it came from ManageIt. You can rotate an endpoint's secret whenever you like.

Retries

Retries and the delivery log

If your server errors or times out, ManageIt tries again on its own, and every attempt shows up in the log with the response. An endpoint that keeps failing is paused until you switch it back on.

One token, one subaccount

A token only sees the client account it was made for.

Two permission checks

A call needs the permission on the token and on the team member behind it.

Requests your way

Set the method, add headers or use a body template to fit the system on the other end.

Paged results

Lists come in pages, with links to the next and previous ones.

Create a token and make a first call

Tokens and webhooks live in each subaccount's settings. Create a token with the permissions you need, then call /api/v1/contacts to see it work.

Read the reference