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

Connections and customer replies to invoices

Connect beel_email to keep a copy of what customers answer to your invoice emails, or register replies from other channels, and receive them by webhook with their attachments.

ChangelogNew

A connection links a company to a service BeeL. works through. With a beel_email connection, the Reply-To of each invoice email also lists an address of BeeL., which keeps a copy of the customer's answer. You can also register replies you receive on WhatsApp, Slack or your own channels. Replies are masked in webhooks and lists, deleted on request and emptied after 12 months.

BeeL. does not store the files of the attachments: each one has a url that returns a temporary download link while the file is available, for a few days after the reply arrives (file_expires_at). To keep a file, download it when invoice.reply.received arrives. Nothing changes for existing integrations.

What else changed

  • Nine new operations under /v1/companies/{company_id}/connections and /v1/companies/{company_id}/invoice-replies, with the privileged scopes connections:read, connections:write, invoice-replies:read and invoice-replies:write.
  • Four new webhooks: connection.connected, connection.disconnected, invoice.reply.received and invoice.reply.deleted, sent only to the account that owns the company.
  • Attachments to download: each attachment carries id, url and file_expires_at; its url returns a download_url valid for about an hour, or null when the file is no longer available.
  • New error codes starting with CONNECTION_ and INVOICE_REPLY_, plus COMPANY_CONNECTION_NOT_FOUND.

Endpoints

  • POST/v1/companies/{company_id}/connectionsConnect a service
  • GET/v1/companies/{company_id}/connectionsList the connections of a company
  • GET/v1/companies/{company_id}/connections/{connection_id}Get a connection
  • DELETE/v1/companies/{company_id}/connections/{connection_id}Disconnect a service
  • GET/v1/companies/{company_id}/invoice-repliesList the replies about invoices
  • POST/v1/companies/{company_id}/invoice-repliesRegister a reply received on your own channel
  • GET/v1/companies/{company_id}/invoice-replies/{reply_id}Get a reply with its full text
  • DELETE/v1/companies/{company_id}/invoice-replies/{reply_id}Delete a reply
  • GET/v1/companies/{company_id}/invoice-replies/{reply_id}/attachments/{attachment_id}Get an attachment with a temporary download link

Where to go next

ConnectionsRead customer repliesDownload attachmentsDelete and retention

Resources under the NIF

An account can now hold several NIFs, each named in the path. The old flat routes are deprecated with a Sunset date and a successor — here's what moved where, when the old routes retire, and how to tell whether it affects you.

Recurring invoices: `series_id` is optional

Creating a recurring invoice without `series_id` no longer answers `VALIDATION_ERROR`: the template uses the company's default series for `invoice_type`. A `STANDARD` template with no default standard series is rejected with `SERIES_DEFAULT_NOT_FOUND`.