Menu
Getting started
Cookbooks
API reference
- Overview
- Companies
- Capabilities
- Measures
- Packages
- Unexplained
- Liquidity forecast
- Portfolio
- Customers
- Invoices
- Collections
- Articles
- Set-offs
- Suppliers
- Supplier invoices
- Supplier payment files
- Bank payments
- Expense claims
- Transactions
- Reconciliation
- Bank accounts
- POS sales
- Webshop orders
- Journal entries
- Voucher gap explanations
- Fiscal periods
- Accounts
- Accrual schedules
- Agreements and commitments
- Tax loss carry-forwards
- Fixed assets
- Documents
- Signing requests
- Company registers
- Capital events
- Owner tax
- Inbox items
- Dimensions
- Employees
- Salary runs
- Reports
- Budgets
- Imports
- Compliance check
- Deadlines
- Skatteverket
- Peppol
- Webhooks
- Operations
- Pending operations
- Health
- API key
- Service accounts
Deadlines
The company's deadlines: the tax and filing deadlines generated from its tax settings and the ones added by hand, with due date, overdue and days left. List them and tick one off or put it back. A deadline is a reminder: ticking it books and files nothing.
Endpoints
GET/api/v1/companies/:companyId/deadlines: List the company's deadlines, the open ones by default.POST/api/v1/companies/:companyId/deadlines/:id/complete: Tick a deadline off, or put it back on the list.
GET /api/v1/companies/:companyId/deadlines
deadlines.list · scope reports:read
List the company's deadlines, the open ones by default.
The deadlines under Deadlines in the app, earliest due date first: tax and filing deadlines generated from the tax settings and the ones added by hand. status open (the default) is what is left to do; completed and all include what is ticked off. A deadline the company removed from its list is never returned. overdue is computed from the due date and only for an open deadline.
Use when: Seeing what is due, or finding the deadline_id to tick off after the work is done.
Don't use for: Which moms periods are on record as filed (GET /reports/vat-declaration/filings, gnubok_list_vat_filings) or what Skatteverket has on file (GET /skatteverket/vat-declarations, gnubok_vat_declaration_status).
Pitfalls
- has_more true means more deadlines match than limit returned: narrow with due_from and due_to.
- A completed deadline says the company ticked it off or a filing was recorded, not that Skatteverket received anything.
Risk: low · Idempotent: yes · Reversible: no · Dry-run supported: no
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
status | "open" | "completed" | "all" | no | open: not ticked off (default). |
due_from | string | no | Earliest due date, YYYY-MM-DD. |
due_to | string | no | Latest due date, YYYY-MM-DD. |
limit | number | no |
Response fields
| Name | Type |
|---|---|
deadlines | object[] |
has_more | boolean |
Example response
{
"data": {
"deadlines": [
{
"deadline_id": "11111111-1111-4111-8111-111111111111",
"title": "Årsredovisning till Bolagsverket",
"due_date": "2026-07-31",
"due_time": null,
"deadline_type": "report",
"tax_deadline_type": null,
"tax_period": null,
"priority": "important",
"source": "user",
"is_completed": false,
"completed_at": null,
"overdue": false,
"days_until_due": 12,
"notes": null
}
],
"has_more": false
},
"meta": {
"request_id": "req_…",
"api_version": "2026-05-12"
}
}
POST /api/v1/companies/:companyId/deadlines/:id/complete
deadlines.complete · scope bookkeeping:write
Tick a deadline off, or put it back on the list.
Sets one deadline completed (is_completed true) or open again (false), as the checkbox under Deadlines in the app does. Only the tick changes: no verifikat, period or filing is touched and nothing is sent to Skatteverket. Asking for the state the deadline already has changes nothing (changed false). Dry-runnable.
Use when: The work a deadline stands for is done (or was ticked off by mistake) and it should leave (or return to) the open list.
Don't use for: A moms or AGI filing made outside Accounted: record the filing instead (moms: POST /reports/vat-declaration/filings or gnubok_mark_vat_period_filed; AGI: gnubok_mark_agi_period_filed), which completes the deadline with the filing date.
Pitfalls
- DEADLINE_NOT_FOUND for an id that is not one of the company's listed deadlines (GET /deadlines, gnubok_list_deadlines), including one the company removed.
- DEADLINE_CONFIRMED_BY_SKATTEVERKET when is_completed false targets a deadline whose filing Skatteverket confirmed through the connection.
Risk: low · Idempotent: yes · Reversible: yes · Dry-run supported: yes · Stage for approval: yes (?stage=true)
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
dry_run | string | no | true (any case) previews the write without committing it, like the X-Dry-Run: true header. Any other value commits. |
stage | string | no | true stages the write for approval instead of committing it: 202 with the pending operation to approve via POST /pending-operations/{id}/approve. Absent or false commits; other values are 400. A reason in the body (why you propose it, at most 500 characters) is shown to the approver as agent_reason and kept with the decision. |
Request body
| Name | Type | Required | Description |
|---|---|---|---|
is_completed | boolean | yes | true ticks the deadline off; false puts it back on the open list. |
Response fields
| Name | Type | Description |
|---|---|---|
deadline | object | |
changed | boolean | False when the deadline already had the requested state. |
Example request
{
"deadline_id": "11111111-1111-4111-8111-111111111111",
"is_completed": true
}
Example response
{
"data": {
"deadline": {
"deadline_id": "11111111-1111-4111-8111-111111111111",
"title": "Årsredovisning till Bolagsverket",
"due_date": "2026-07-31",
"due_time": null,
"deadline_type": "report",
"tax_deadline_type": null,
"tax_period": null,
"priority": "important",
"source": "user",
"is_completed": true,
"completed_at": "2026-07-19T08:30:00.000Z",
"overdue": false,
"days_until_due": 12,
"notes": null
},
"changed": true
},
"meta": {
"request_id": "req_…",
"api_version": "2026-05-12"
}
}