In the app, invoices and estimates are for owners and admins. The REST API was looser: a manager's personal access token could list and read every invoice and estimate, and download an invoice as a UBL e-invoice. It now matches the app.
This changes what existing integrations get. If an integration uses a
manager's token to read invoices or estimates, those requests now answer
403, with the usual {"message": "…"} body, instead of the data. Every
/api/v1/invoices and /api/v1/estimates endpoint behaves this way, reading
and writing alike. A manager's token was already refused when it tried to
create, change, send or delete an invoice or estimate; reading is what is new.
What does not change:
- An admin's or owner's token works as before.
- An organization key works as before: with read access it reads invoices and estimates, and with write access it can also create and change them.
- A member's token was already refused, and still is.
- The uninvoiced report (
/api/v1/reports/uninvoiced) is about time, not invoices, and still answers a manager's token.
To keep such an integration working, have an admin or owner create its token.
Organization keys are now managed by owners and admins only. An organization key acts for the whole workspace, invoices included, so a manager who could create one could get around the rule above. On the Developer page a manager now sees a note in place of the keys table, and creating, listing or revoking an organization key is refused for anyone below admin. A manager's own personal access tokens are untouched.
Keys a manager created before this change keep working: nothing was revoked. An owner or admin can see them on the Developer page and revoke any that should not exist.
The API reference and the OpenAPI document now also list these refusals, and
the answers a member's token has received since October: 404 for a project
the member is not assigned to or for another person, and 422 for a time
entry whose project, task or person is not in the workspace.