Resources

Support

How to get help with your integration.

Contact#

support email or URL

What to include#

  • Your organization's name, and whether it's staging or production.
  • What you sent and what you got back: the method, path, status and error code.
  • Ids that help us find it: the invoice number or id, the customer id, the Flux-Event-Id or the delivery id.
  • When it happened, with the time zone.
Keep secrets out of support requests

Never send an API key, a webhook secret or a customer's personal data. If a key may have leaked, ask your organization's admin to revoke it first.

Before you write#

  • 401: check the header is Authorization: ApiKey flx_live_…, and that the key hasn't been revoked.
  • 403 insufficient_scope: details.required names the scope the key needs.
  • Webhooks not arriving: check the endpoint is active and look at the delivery log.
  • Signatures failing: test your code against the worked example.