e-conomic

e-conomic needs two tokens, and they come from different places.

1. The App Secret Token identifies your application. You get it once, from e-conomic, when you register as a developer partner at secure.e-conomic.com/secure/api1/requestaccess.aspx. It is the same for every customer you connect.
2. The Agreement Grant Token identifies the customer's agreement (their e-conomic company). The customer grants it by going through e-conomic's app-authorisation URL for your app; each customer produces a different one.
3. Set ECONOMIC_APP_SECRET_TOKEN and ECONOMIC_AGREEMENT_GRANT_TOKEN.

Both travel as headers on every request — X-AppSecretToken and X-AgreementGrantToken. A 401 here means one of the two is wrong, and the message does not say which.

One connector, one agreement. The grant token binds this connector to one company. A bookkeeper with several clients needs one connector per client.

Booked vs drafts vs not-due. e-conomic splits invoices across three collections: /invoices/drafts (not yet booked — not revenue), /invoices/booked (posted and immutable), /invoices/not-due and /invoices/overdue (booked and unpaid, split by due date). Summing drafts with booked over-reports; the overdue collection is the direct answer to 'who is late'.

Paging is skippages and pagesize (max 1000). The response's pagination block carries results, resultsWithoutFilter and the link to the next page.

Filtering uses e-conomic's own syntax: filter=date$gte:2026-01-01$and:date$lte:2026-03-31. Operators are $eq, $ne, $gt, $gte, $lt, $lte, $like, $in, joined with $and: and $or:.

Cloud reachability: restapi.e-conomic.com is public with a valid certificate.