Integration options
Match the way you integrate Paylode to your team and the surface you're putting it on — so you write the least code that gets you what you need.
There are three ways to bring Paylode into your product, and they trade effort for control:
- Embed — drop a small script and a container onto a page you already have. Paylode renders a branded perks center inside it. No API calls from your code.
- Hosted — send people to a Paylode-hosted page at your own subdomain. No code at all; you just link to it.
- API — call Paylode's API directly and render everything yourself. Full control, and the only way to build a fully custom experience.
Most teams start with an embed or a hosted page and adopt the API only where they need to compose the experience themselves. You can mix them: a hosted perks page for marketing emails, an embed inside your logged-in app, and API calls for a bespoke checkout reward — all on one account.
Choosing a path
| Path | Choose it when | Effort | Example |
|---|---|---|---|
| Embed | You can add HTML to a page and want a branded perks center fast. | Paste three lines; no build step. | A rewards tab in your logged-in dashboard. |
| Hosted | Your CMS blocks scripts, or you just want a link to share. | None — link or QR code. | A "Member Perks" link in a newsletter. |
| API | You need to control layout, filtering, or the redemption flow yourself. | A real integration; you render everything. | A perks section styled to match your checkout. |
If you can edit a page's HTML, the embed is the fastest route to something live. Reach for the API when the embed's layout isn't enough — when you want your own components, your own filtering, or perks composed into a screen you fully own.
Boost is API-only
Boost reward journeys — "do this, get that" campaigns — are driven through the API and the Boost page embed, not the no-code perks center. If your program is a Boost campaign rather than a perks page, plan for a developer. See Create a Boost campaign.
No-code vs. needs-an-engineer
A product manager can run a surprising amount of Paylode from the admin app alone. Use this to see, at a glance, what your team can self-serve and what needs a developer.
| Capability | No-code (admin app) | Needs an engineer |
|---|---|---|
| Build and brand a perks center (colors, fonts, layout) | ✓ | |
| Choose and rank which perks appear | ✓ | |
| Use a Paylode-hosted perks page | ✓ | |
| Manage your team and profile | ✓ | |
| Restrict access by IP | ✓ | |
| Embed a perks page on your own site | Container is configured in-app | Paste the snippet once |
| Migrate your existing perks program | We set it up with you | |
| Build a fully custom perk page | ✓ | |
| Sync perks into a CMS | ✓ | |
| Run a Boost campaign end to end | Create/configure in app where supported | ✓ (customer journey) |
| Order gift cards / hand out reward links | ✓ | |
| Query your analytics | ✓ |
"Needs an engineer" doesn't mean a large project — embedding a perks page is three lines pasted once. It's a rough map of where a developer has to touch the code, not a measure of effort.
Where to go next
- Embed: Embed a perks page — the actual snippet, placed on your site.
- Hosted: Use a hosted perks page — resolve your subdomain and share it.
- API: Build a custom perk page — render perks yourself against the API.
Whichever you pick, Authentication and Platform basics apply once you're calling the API, and Verify your deployment confirms it's live.