Award EP via Webhook

This guide is for partner developers integrating the award EP (tích điểm) channel. When a user completes a qualifying action on your side (an order, a check-in, a campaign event), you call one signed HTTP endpoint and Eventista credits EP to that user’s wallet.

The award is settled synchronously: by the time you get a 202, the EP is already in the user’s wallet and the status endpoint reports COMPLETED immediately.

Server-to-server HMAC-SHA256 signed Idempotent JSON over HTTPS

Where this runs

The endpoint is served by the Eventista EP engine (the single writer of the EP ledger). You only ever talk to the public webhook URL — you never touch the database or the back-office directly.

Concepts

Term	Meaning
EP	E-point, the unit credited to a user wallet.
Partner	Your integration. Identified by an apiKeyId and authenticated with an HMAC secret.
Tenant	An Eventista workspace (tenantId). Your partner account is allow-listed to one or more tenants.
User	The EP recipient, identified by email (normalized to lowercase on our side).
orderId	A partner-unique id for one award. Drives idempotency — reuse it to safely retry, change it for a new award.
Caps	Per-transaction and per-day ceilings on credited EP. Mandatory and enforced server-side.

Endpoints

Method	Path	Purpose
POST	/v1/ep/webhook	Award EP to a user.
GET	/v1/ep/webhook/transactions/{orderId}	Look up the status of a single award.
GET	/v1/ep/webhook/awards	List all your awards in a tenant.

Full URL: {BASE_URL}/v1/ep/webhook.

Next steps

Onboarding & credentials The apiKeyId, secret, base URLs, and caps you receive.

Authentication The HMAC signature scheme and what each endpoint signs.

Award endpoint Body, raw→EP conversion, caps, and responses.

Integration checklist Everything to confirm before going live.