e-bon
e-bon.ro
Portal

API

The Portal's API surface — manage the credentials POS partners and external systems use to talk to the e-bon API, and the webhook endpoints e-bon uses to push events back to your systems.

API

The API section of the Portal groups every machine-to-machine surface in one place. It mirrors the portal app's API tab shell at /portal/api, which itself splits into two views — Keys and Webhooks — covering the two halves of any integration with the e-bon platform.

  • Keys — create, scope and revoke the API keys POS partners and external systems use to authenticate against the e-bon REST API. Keys are how an external system pulls data from e-bon: send a key in the Authorization header and read receipts, devices, reports or queue commands within the scopes granted to that key.
  • Webhooks — configure the HTTPS endpoints e-bon pushes signed event payloads to when something happens (a receipt is issued, a Z report closes, a device goes offline). Webhooks are how your systems learn about events the moment they occur — no polling.

Most integrations use both: an API key so your system can read and act on e-bon data, and one or more webhook subscriptions so e-bon can notify your system the moment a relevant event fires.

Listing keys and webhooks is available to anyone in the organization, but creating, editing, deleting, testing or rotating any of these credentials is restricted to the Owner and Admin roles. If the relevant buttons are missing, ask your organization owner to grant you the right role.

Next steps

  • Keys — the read-side credential. API keys pull data.
  • Webhooks — the push-side subscription. Webhooks deliver events.
  • API reference — the full machine-readable surface those keys and webhooks talk to.

New receipt

Issue a fiscal receipt from the e-bon Portal — pick a connected device, build the receipt in the browser, and watch the print status update live.

API keys

Create, scope and revoke the API keys that POS partners and external systems use to talk to the e-bon API — and learn where webhooks fit in alongside them.