Skip to main content

Get help

Stuck, or seeing something that doesn't match these docs? Here's how to reach us and what to include so the first reply is the useful one.

Where to ask​

  • Your Paylode point of contact — the fastest route for anything about your account: enabling features, onboarding questions, commercial topics.
  • support@paylode.com — technical questions and problem reports.

What to include in a problem report​

The more of these you include, the faster the answer:

  • What you called — the host, method, and path (for example GET https://perk-collections.paylode.com/perk-collections/spring-rewards), or which page surface (embed, hosted page, Boost page).
  • When — timestamp with timezone.
  • What came back — the HTTP status and response body. For a 5xx, include the requestId from the body — it points us at your exact request. See Error handling for what each response carries.
  • The ids involved — collection slug, perk id, campaign id.
  • Never include your API key — we don't need it, and a key that's been shared should be treated as compromised.

Before you write in​

Two checks resolve a lot of reports on the spot:

  • Verify your deployment — confirms the integration is live and shows you the exact failing request in the browser.
  • The Troubleshooting section at the bottom of the guide you're following — each guide lists its own known gotchas.