Chaser

BUSINESS · COMMERCE & FINANCE

Customers, invoices, payment history, and chasing schedules in that organisation.

Connecting Chaser in practice

Chaser allows 200 requests per minute and waives the limit entirely for the first 24 hours after an organisation is created, so the initial sync gets a free pass the ongoing integration does not. Bad credentials come back as 403 forbidden_error rather than 401, and bulk upserts are capped at 100 entries per request.

Rate limits

200 requests per minute. Exceeding it returns 429 with {"type":"rate_limit_error","message":"Rate limit exceeded, retry in 1 minute"}.
Rate limiting is waived for the first 24 hours after the organisation is created, to simplify the initial sync.
List endpoints: limit 1–100 with a default of 100, and page numbering starts from 0.
Bulk upsert endpoints accept up to 100 items per request.

Who has to approve

There is no per-user OAuth flow. Someone with access to the Chaser organisation has to create the organisation, choose API from the list of accounting systems, click Connect with API, and then issue a key and secret under Organisation Settings → Integrations — so access is granted and revoked in the tenant’s own settings rather than by the connecting user.

Worth knowing

An invalid API key or secret returns 403 forbidden_error, not 401, so code that treats 403 as "wrong permissions" will misread a rotated credential.
Resources can be addressed by internal id or by the source system’s identifier with an ext_ prefix (/v1/customers/ext_1234), which removes the need to store Chaser’s own IDs — but the two forms live in the same path slot.
Invoice status drives visibility, not a separate flag: PAID invoices stay visible for six months after the fully paid date and are then archived out of the database, while DRAFT, SUBMITTED, VOIDED and DELETED are invisible, send no reminders and are excluded from every report.
Filtering uses bracketed operators — status[ne]=AUTHORISED, amount_due[gte]=1000, invoice_id[in]=1,2,3 — combined only as logical AND, and the supported operators differ per field.

Checked against Chaser API OpenAPI specification (2026-09-29), Connect to Chaser using Chaser API (2026-09-29)

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

chaser_delete_v1_customers_by_customer_id_contact_persons_by_contact_person_idWRITE

Delete contact person via DELETE /v1/customers/{customer_id}/contact_persons/{contact_person_id}.

api

chaser_delete_v1_customers_by_customer_id_notes_by_note_idWRITE

Delete customer note via DELETE /v1/customers/{customer_id}/notes/{note_id}. Delete a note from a customer

api

chaser_delete_v1_templates_by_template_idWRITE

Delete template via DELETE /v1/templates/{template_id}. Delete a template. A template cannot be deleted if it is being used in a schedule.

api

chaser_get_statusREAD

Service status via GET /status. Liveness check for the Chaser API. Needs no credential and answers 200 with the plain text "OK" (measured 2026-09-16); it is the only path outside the /v1 prefix that ships. Use it to tell a Chaser outage apart from a credential problem: a 403 on a /v1 call with this answering 200 means the key, not the service.

api

chaser_get_v1_credit_notesREAD

Get credit notes via GET /v1/credit_notes.

api

chaser_get_v1_credit_notes_by_credit_note_idREAD

Get credit note by id via GET /v1/credit_notes/{credit_note_id}.

api

chaser_get_v1_customersREAD

Get customers via GET /v1/customers.

api

chaser_get_v1_customers_by_customer_idREAD

Get customers by id via GET /v1/customers/{customer_id}. Get customer by id.

api

chaser_get_v1_customers_by_customer_id_contact_personsREAD

Get contact persons via GET /v1/customers/{customer_id}/contact_persons.

api

chaser_get_v1_customers_by_customer_id_contact_persons_by_contact_person_idREAD

Get contact person by id via GET /v1/customers/{customer_id}/contact_persons/{contact_person_id}.

api

chaser_get_v1_customers_by_customer_id_notesREAD

Get customer notes via GET /v1/customers/{customer_id}/notes. Get notes for a customer

api

chaser_get_v1_invoicesREAD

Get invoices via GET /v1/invoices.

api

chaser_get_v1_invoices_by_invoice_idREAD

Get invoice by id via GET /v1/invoices/{invoice_id}.

api

chaser_get_v1_invoices_by_invoice_id_historyREAD

Get invoice history by id via GET /v1/invoices/{invoice_id}/history.

api

chaser_get_v1_invoices_historyREAD

Get invoice history via GET /v1/invoices/history.

api

chaser_get_v1_organisationREAD

Get current organisation via GET /v1/organisation.

api

chaser_get_v1_organisationsREAD

Get organisations via GET /v1/organisations.

api

chaser_get_v1_overpaymentsREAD

Get overpayments via GET /v1/overpayments.

api

chaser_get_v1_overpayments_by_overpayment_idREAD

Get overpayment by id via GET /v1/overpayments/{overpayment_id}.

api

chaser_get_v1_schedulesREAD

Get schedules via GET /v1/schedules. Get all schedules for the organisation

api

chaser_get_v1_schedules_by_schedule_idREAD

Get schedule by id via GET /v1/schedules/{schedule_id}. Get a schedule by id

api

chaser_get_v1_tasksREAD

Get tasks via GET /v1/tasks.

api

chaser_get_v1_templatesREAD

Get templates via GET /v1/templates. Get all templates for the organisation

api

chaser_get_v1_templates_by_template_idREAD

Get template by id via GET /v1/templates/{template_id}. Get a template by id

api

chaser_patch_v1_customers_by_customer_id_notes_by_note_idWRITE

Update customer note via PATCH /v1/customers/{customer_id}/notes/{note_id}. Update a note on a customer

api

chaser_patch_v1_tasks_by_task_idWRITE

Update task via PATCH /v1/tasks/{task_id}. Update a task status, assignee, due date, or metadata

api

chaser_post_v1_chasing_pauseWRITE

Pause organisation chasing via POST /v1/chasing/pause. Pause chasing for the entire organisation. No invoices will be chased until resumed.

api

chaser_post_v1_chasing_resumeWRITE

Resume organisation chasing via POST /v1/chasing/resume. Resume chasing for the entire organisation.

api

chaser_post_v1_credit_notesWRITE

Create credit note via POST /v1/credit_notes.

api

chaser_post_v1_customersWRITE

Create customer via POST /v1/customers.

api

chaser_post_v1_customers_by_customer_id_chasing_pauseWRITE

Pause customer chasing via POST /v1/customers/{customer_id}/chasing/pause. Pause chasing on a customer. All invoices for this customer will not be chased until resumed.

api

chaser_post_v1_customers_by_customer_id_chasing_resumeWRITE

Resume customer chasing via POST /v1/customers/{customer_id}/chasing/resume. Resume chasing on a customer. All invoices for this customer will be chased again.

api

chaser_post_v1_customers_by_customer_id_contact_personsWRITE

Create contact person via POST /v1/customers/{customer_id}/contact_persons.

api

chaser_post_v1_customers_by_customer_id_notesWRITE

Create customer note via POST /v1/customers/{customer_id}/notes. Create a note on a customer

api

chaser_post_v1_invoicesWRITE

Create invoice via POST /v1/invoices.

api

chaser_post_v1_invoices_by_invoice_id_chasing_pauseWRITE

Pause invoice chasing via POST /v1/invoices/{invoice_id}/chasing/pause. Pause chasing on an invoice. The invoice will not be chased until resumed.

api

chaser_post_v1_invoices_by_invoice_id_chasing_resumeWRITE

Resume invoice chasing via POST /v1/invoices/{invoice_id}/chasing/resume. Resume chasing on an invoice.

api

chaser_post_v1_organisation_syncWRITE

Sync organisation. via POST /v1/organisation/sync. Sync organisation. Rate-limit 5 requests per 1 hour.

api

chaser_post_v1_overpaymentsWRITE

Create overpayment via POST /v1/overpayments.

api

chaser_post_v1_schedulesWRITE

Create schedule via POST /v1/schedules. Create a new schedule

api

chaser_post_v1_schedules_by_schedule_id_assignWRITE

Assign schedule to customers via POST /v1/schedules/{schedule_id}/assign. Assign a schedule to customers. This sets the chasing schedule for the given customers.

api

chaser_post_v1_tasksWRITE

Create task via POST /v1/tasks. Create a task

api

chaser_post_v1_templatesWRITE

Create template via POST /v1/templates. Create a new template

api

chaser_put_v1_bulk_credit_notesWRITE

Bulk Upsert credit notes. via PUT /v1/bulk/credit_notes. Bulk Upsert up to 100 credit notes, matching by credit_notes_id (or id).

api

chaser_put_v1_bulk_customersWRITE

Bulk Upsert customers. via PUT /v1/bulk/customers. Bulk Upsert up to 100 customers, matching by external_id (or id).