Skip to main content

Support

If something doesn't work as these docs say, or you need a limit raised, write to us.

Contact​

Email support@getreeds.co.

What to include​

A good request lets us find your call quickly. Include:

  • The X-Request-Id header from the response. Every call is in Dashboard → Developers → API requests for 30 days, with its X-Request-Id.
  • Whether it happened in Test or Live mode (livemode in the response)
  • The delivery id (dlv_...), quote id or address id involved
  • The time of the request, with your timezone
  • The Reeds-Event-Id (evt_...) for a webhook problem
  • The error code and the HTTP status you received
  • What you expected to happen
danger

Never send your client secret (rcs_...), an access token or your webhook signing secret (whsec_...) to anyone, including Reeds support. We never need them. If you shared one by mistake, rotate it in Dashboard → Developers.

Before you write​

  • Check the error page for the code you got.
  • For webhook problems, open the event log in Dashboard → Developers. It shows each attempt and your server's response, and you can resend the event.
  • Check whether you are in the right mode. Test and Live have separate credentials and data.

Outages​

Reeds has no status page. If you suspect an outage, email support@getreeds.co with one X-Request-Id and the time of the request.

Changelog​

Every public API change is recorded on the changelog. Breaking changes are also emailed to every account with live credentials. See Versioning.

Next steps​