Skip to main content
Every request between Bindbee and a source system is recorded here. Come to this page once sync status and the error’s source have left the question open.
A model reported Skipped or Not Supported was never requested, so the logs hold no entry for it. Sync status settles both.

​
Where to find them

Open Logs in the dashboard for the whole account, or open a single connector to scope it to that customer. Scoping to the connector is faster.
The Logs view in the Bindbee Dashboard, listing requests by connector

​
What an entry holds

Read the upstream response body first. Bindbee keeps the source system’s own answer verbatim, and that body names the permission or field at fault - see Origin-system errors.

​
Find an answer

​
Connector logs are dashboard-only

There is no API for them. Anything your own monitoring acts on has to come from sync webhooks or the connector’s status and sync_status fields.

​
Webhook delivery logs are separate

They record Bindbee’s attempts to reach your endpoint, so they answer why your handler stayed quiet. Those do have an API: List Webhook Logs, and the dashboard keeps them on the Webhooks tab under Logs. Each response_code is explained on Delivery and retries.
A webhook's page showing its delivery log, filterable by Event, Status, Date and Error only, with each row's webhook action, method, URL and response status

​
Limits

  • An empty field. A 200 with the field absent leaves no error to find. That’s scope, permissions, or the unified model - see Scoping.
  • An upstream deletion. A record disappearing produces no request, so no entry.
  • Retention. The window is unpublished, so treat logs as a recent-debugging tool rather than an audit trail.