NewConnections and customer replies to invoices
BeeL
Get startedMulti-NIFVeriFactuRulesStripeAPI referenceChangelog

Permissions

Which scopes and access levels connections and customer replies need, and why they are never on a key by default.


Connections and replies handle data of third parties, so their four scopes are privileged: a key only holds them if you tick them when you create it. A key created without choosing scopes does not. The scope table is in Scopes.

ScopeLets the key
connections:readRead connections, and subscribe a webhook to connection.*.
connections:writeConnect and disconnect services.
invoice-replies:readRead replies with their full text, download their attachments, and subscribe a webhook to invoice.reply.*.
invoice-replies:writeRegister and delete replies.

Who can use them

The scope is a ceiling, and the role of the user who owns the key, or the access level of the account that manages the company, is a second one.

Whoinvoice-replies:readinvoice-replies:writeconnections:read and :write
OWNER and ADMIN of the account that owns the companyYesYesYes
Member with a grant at OPERATE, and an account that manages the company at OPERATEYesYesNo
Member with a grant at VIEW, and an account that manages the company at VIEWYesNoNo

What answers when something is missing:

StatusCodeCause
403INSUFFICIENT_SCOPEThe key lacks the scope.
403COMPANY_READ_ONLYThe role or access level is not enough: connections are for OWNER and ADMIN of the owning account, writing replies needs write access.
403ACTIVE_COMPANY_NOT_ACCESSIBLEThe company is not one of yours, or does not exist. Both answer the same.

Webhooks go to the owner

connection.* and invoice.reply.* events are delivered only to the endpoints of the account that owns the company, never to an account that manages it. A managing account can still read the replies with GET …/invoice-replies when it holds the scope.