Developer platform
Build on the same controlled operations used by RebateCardX portals.
Use versioned REST resources, scoped machine credentials, idempotent mutations, cursor pagination and signed events.
Route recovery
Return an unmatched request to a known Rebate Cards path.
The requested route is outside the current website map, so navigation returns to published program information.
- 01 / Request
Unknown pathname
A browser asks for a route that is not present in the current site map.
- 02 / Router
Path resolution
- Normalise the request
- Compare published routes
- Preserve a clear 404 response
- 03A / Option
Return home
Restart with the main Rebate Cards business-model overview.
- 03B / Option
Explore industry models
Continue to rebate models, economics, insights or contact.
- 04 / Website
Published navigation
Only current, intentional destinations are presented as available pages.
- 05 / Recovery
A valid next request
The visitor selects a known destination and resumes the information journey.
Base URL
https://api.rebatecardx.com/api/v1
Credentials are issued to a tenant and scope. They never grant access to another merchant or raw card data.
- 01
Versioned contract
All merchant endpoints are rooted at /api/v1 and changes preserve an explicit compatibility boundary.
- 02
Idempotent money movement
Financial, award, claim and provider mutations require an Idempotency-Key.
- 03
Explicit concurrency
Versioned resources use ETag and If-Match instead of silent last-write-wins updates.
- 04
Signed events
Outbound events carry a delivery identifier, timestamp and signature for independent verification.