Security

  • We require the operator to generate an API key for access to the Operator API by BetLink's backend. The BetLink backend will send this API key to the operator endpoints in a header named 'X-API-Key'.

  • We strongly recommend that access to the API is locked down and that BetLink's IP ranges are added to a per environment allow-list.

  • All exposed endpoints which will handle IMGA communication should support TLS v1.2 or higher.

  • User IDs sent to BetLink by the operator should be encrypted in such a way that they are not possible to decrypt for the BetLink platform (i.e. using a key unknown to BetLink). They should always be encrypted in the same way (so that the same user id will always generate the same encryption result) and the operator should be able to easily decrypt them to reveal the original user ID.

PreviousIntroductionNextIdempotency

Last updated