Skip to main content

Sync Lifecycle

Use this when you need to confirm there is no polling or long-running sync. Each onboarding event is one webhook in and one callback out.

What happens​

  1. B1Link — When onboarding reaches the sync point, B1Link creates an ERP event and POSTs the payload to your webhook URL.
  2. Your webhook — Receives the JSON. You read onboardingRequestErpEventId and the supplier data.
  3. Your ERP — You create or update the vendor and assign a vendor number.
  4. Your code — You PUT that event ID and vendor number to B1Link with X-B1LINK-Signature. One request per event.
  5. B1Link — Returns 204 and updates the event; onboarding completes.

There is no second webhook and no polling. If you need to resend, use the same event ID and body; B1Link behaviour for duplicates is defined by your configuration (idempotency on your side is still required).

Next steps​