FAQs - Platform RX (Reactive) Events & Player Model

Which reactive events are mandatory for pure-gamification setups?

At minimum: game, sport, and money transaction events, plus bonus-granted. Player events such as registration, login, opt-in, and KYC/account verified should also be sent.

How do Operators publish “bonus granted” as a reactive event?

Operators should POST to /rx-api/transactions/v1/bonus-granted with the required payload and expect a 202 Accepted response on success.

Where do Operators manage player tags programmatically?

Operators can use the Platform REST Player Tags endpoints (for example, PATCH /rx-api/players-data/v1/tags/upsert) to create or update tags that feed segmentation.

Can Operators block specific players from CRM marketing?

Yes. Operators can use the Risk module; players flagged as “at risk” are excluded from CRM communications until cleared.

What authentication applies to Player, Tag, and Risk REST endpoints?

Platform OAuth2 Client Credentials (JWT in header) authentication applies.

Is there any guidance on retries for RX calls?

Yes. Operators should implement retries with exponential backoff for transient errors or timeouts as a best practice.

Do reactive events replace data loads?

No. Operators should use ingestion for initial or bulk synchronization and reactive events for immediate processing. Both methods complement each other.

Is there a separate authentication scope per RX stream?

No. A single Platform OAuth token is sufficient for all RX endpoints.