Gamification for your product, as an API.

Integrate my application with the Gamification Engine (https://gamification.one), a REST API that turns what users do into XP, levels, credits, collectible cards, team-game progress and loyalty tiers.

Connection
- Read the base URL and API key from configuration: GAMIFICATION_API_BASE and GAMIFICATION_API_KEY. The key is a server-side secret: never send it to a browser or mobile app, never commit it.
- Send it as the X-Api-Key header on every request. Bodies are JSON with camelCase fields; enum values are numbers.
- Errors are RFC 7807 problem+json: 400 invalid input, 401 bad key, 404 unknown participant or action, 409 a rule said no (for example a daily cap was reached).

1. Define the reward-worthy actions (a one-time setup script; a 409 means the key already exists)
POST /api/actions
{"key": "closed_deal", "name": "Closed a deal", "xpReward": 50, "creditReward": 10}
Rewards per amount, e.g. 2 XP + 1 credit per euro spent, at most 5 times a day:
{"key": "purchase", "name": "Purchase", "xpReward": 0, "creditReward": 0, "rewardMode": 1, "xpPerUnit": 2, "creditsPerUnit": 1, "dailyCap": 5}
Look through my codebase, propose the actions that fit it with their rewards, and wait for my confirmation before creating them.

2. Register users as participants (idempotent: a known externalUserId returns the existing participant)
POST /api/participants
{"externalUserId": "<my user id>", "displayName": "Jane Doe", "email": "jane@example.com", "type": 0}
type 0 = employee, 1 = customer. Call it when a user is created, plus a one-off backfill for existing users.

3. Send an event whenever one of those actions happens
POST /api/events
{"externalUserId": "<my user id>", "actionKey": "closed_deal"}
Add "amount": 49.90 for per-amount actions. The response says what the event caused: xpAwarded, creditsAwarded, totalXp, totalCredits, levelBefore, levelAfter, leveledUp, drop (a collectible card, or null) and gameScoreUpdates. A 404 for the participant means they were never registered: register them, then send the event once more.

How to build it
- One small client in my backend, in the language and HTTP library my project already uses, with configurable base URL and timeouts.
- Send events after my own transaction commits. A gamification failure must never break the user's action: log it instead of failing the request. Events are not deduplicated, so don't retry blindly after a timeout.
- Where my UI has a natural place for it, show level-ups and card drops; ask me before adding new screens.
- Add tests with the HTTP calls mocked.

Optional, ask me first
- Leaderboard: GET /api/participants/leaderboard (?type=Customer ranks customers).
- Customer loyalty widget: my backend mints a short-lived token with POST /api/participants/{id}/tokens and renders
  <script src="{GAMIFICATION_API_BASE}/widget/loyalty-widget.js" data-api-base="{GAMIFICATION_API_BASE}" data-token="{token}" data-target="#loyalty"></script>
  and the site's origin is registered once with POST /api/widget-origins {"origin": "https://shop.example.com"}.