Release 2026.10.02-R1

Webhooks

• You can now limit a webhook to the branches and source channels it should receive notifications for. In Settings → Workspace Settings → API Keys & Webhooks, restrict each webhook by branch, by source channel, or both. If you select the API channel, you can also narrow it to specific API keys. A webhook restricted on both receives only documents that match both. For example, a webhook limited to two branches and to SFTP receives SFTP documents from those two branches and nothing else. A webhook you leave unrestricted keeps receiving every notification, so your existing webhooks are unchanged. You can change a webhook's restrictions at any time. The change applies to notifications sent after it, and earlier notifications are not resent.
• Each webhook notification now also includes the document's branch, its source channel and, for a document submitted through the API, the API key that submitted it. The existing fields are unchanged.
• If you delete a branch that a webhook is limited to, JomeInvoice warns you first and names the webhooks that use it. The webhook keeps the deleted branch in its restrictions, so it stops receiving notifications for that branch; it does not start receiving everything.

API keys

• Each API key now has a Data access setting that controls which of your workspace's documents it can work with: Entire workspace, Only this credential's documents, or Reporting, which can read every document but cannot create, change or cancel anything. Your existing keys are set to Entire workspace, so current integrations are unchanged. A key you create now starts on Only this credential's documents unless you choose otherwise. A key limited to its own documents lists and retrieves only the documents it submitted, not documents that reached JomeInvoice another way, such as by upload or SFTP, or documents from before 10 August 2026. It is refused if it tries to cancel a document submitted with another key.