Skip to main content
The compliance calendar is read-only. Reading it never triggers a filing, a recomputation, or any side effect — it reflects what doola already tracks for the company.
A company’s compliance calendar lists the recurring obligations doola tracks to keep it in good standing. Today it returns a single obligation — the annual report — with its next due date and a derived status. The response is a list, so future obligation types slot in as additional entries without a breaking change.

​
Retrieving the calendar

The full request and response schema is in the Compliance section of the API reference. A successful response:

​
Statuses

status is derived at read time from the resolved due date and the company’s state:
The annual-report event is always returned — even for an unsupported state or a company that is too new. The status carries the reason and the date fields are null, so you never receive an empty list you have to disambiguate.

​
Roll-forward

The annual report recurs each year. Once a report is filed, nextDueDate advances to the next occurrence and lastFiledDate records when the previous one was filed — so a future due date is always explainable to the customer.

​
Errors

Ownership is enforced the same way across the Partner API: a company that exists but isn’t yours returns 404, never 403, so existence cannot be probed across partners. See Errors.