Client Data Integration

Overview

---

This document summarises the options available to integrate with Future Anthem, for both data ingress and egress.

Future Anthem offers Standard as well as Client Bespoke integration options for either Real-time or Batch Data.

This document also outlines the options available to provide large datasets to Future Anthem on a one-off or irregular basis.

 

Standard Integrations

---

The standard Integration of Future Anthem products with client systems is via API’s:

 

Real-Time Data Integration

Future Anthem’s Standard Real-time Data Integration uses Azure Event Hubs, which provide clients with a widely supported standard technology to integrate with Anthem’s Real-time Engine.

Sending Events to Anthem Azure Event Hubs supports sending event data via

• REST API
• AMQP 1.0
• SDK for many different programming languages

 

Sending Events via REST API

Request

 

 

Request Headers

 

Request Body

JSON formatted event data. Either a single event or a list of batched events.

All JSON payloads have to be String escaped and passed as the value to the “Body” key

{ 
  "$schema": "http://json-schema.org/draft-07/schema", 
  "$id": "http://example.com/example.json", 
  "type": "array", 
  "title": "Real-time Event Upload", 
  "description": "Schema definition for real-time events uploaded to Future Anthem", 
  "default": [], 
  "examples": [ 
 [ 
  { 
   "Body": "{\"GameId\":\"1\",\"PlayerId\":\"123\",\"SpinId\": 1,\"Amount\": 0.25}" 
  } 
 ] 
], 
"additionalItems": true, 
"items": { 
 "$id": "#/items", 
 "anyOf": [ 
   { 
    "$id": "#/items/anyOf/0", 
    "type": "object", 
    "title": "Event Schema", 
    "description": "The schema of a single event", 
    "default": {}, 
    "examples": [ 
      { 
        "Body": "{\"GameId\":\"1\",\"PlayerId\":\"123\",\"SpinId\": 1,\"Amount\": 0.25}" 
      } 
    ], 
    "required": [ 
      "Body" 
    ], "properties": { 
         "Body": { 
            "$id": "#/items/anyOf/0/properties/Body", 
            "type": "string", 
            "title": "Event Body Schema", 
            "description": "The event Payload", 
            "default": "", 
            "examples": [ 
              "{\"GameId\":\"1\",\"PlayerId\":\"123\",\"SpinId\": 1,\"Amount\": 0.25}" 
            ] 
          } 
        }, 
        "additionalProperties": true 
      } 
    ] 
  } 
}

 

• Future Anthem will translate the client's data schema to the internal data schema used by Anthem’s Real-time Engine

• The event data provided can follow any schema and can be nested

• Clients should provide their schema documentation, allowing Anthem to configure their internal schema transformation

Response

The response includes:

• an HTTP status code

• a set of response headers

• a response body

• If the request is successful, the response body is empty

• If the request isn't successful, the body contains an error code and error message

 

 

Example

POST /spins/messages?timeout=60&api-version=2014-01 HTTP/1.1 
Host: https://casinomagic-fane01.servicebus.windows.net 
Authorization: SharedAccessSignature sr=casinomagicfane01.servicebus.windows.net&sig=casinomagic-token&se=1657122931&skn=upload 
Content-Type: application/vnd.microsoft.servicebus.json

[{"Body": "{\"GameId\":\"1\",\"PlayerId\":\"123\",\"SpinId\": 1,\"Amount\": 0.25}"}]

curl --location --request POST 'https://casinomagic-
fane01.servicebus.windows.net/spins/messages?timeout=60&api-version=2014-01' \ 
--header 'Content-Type: application/vnd.microsoft.servicebus.json' \ 
--header 'Authorization: SharedAccessSignature sr=https%3A%2F%2Fcasinomagic
fane01.servicebus.windows.net%2Fspins&sig=casinomagic-token&se=1657122931&skn=upload' \ 
--data-raw '[{"Body": "{\"GameId\":\"1\",\"PlayerId\":\"123\",\"SpinId\": 1,\"Amount\": 0.25}"}]'

 

 

Sending Events via AMQP 1.0

AMQP integration is documented as part of Azure’s Service Bus: https://docs.microsoft.com/enus/azure/service-bus-messaging/service-bus-amqp-overview

 

Sending Events via SDK

The Azure SDK exists for all major programming languages:

• Python: https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-python-getstarted-send

• .NET https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-dotnet-standardgetstarted-send

• Java https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-java-get-started-send

• JS https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-node-get-started-send

• Others https://docs.microsoft.com/en-us/azure/event-hubs/

  
  

Recieving Events from Anthem

• To receive real-time events, an API should be provided for Anthem to call

•  Anthem integrates with the Client API’s based on their provided specifications and requirements

  
  
  

Anthem supports:

• POST method to APIs

• Static IPs for IP whitelisting

• SSL with self-signed client certificates

  
  

If clients do not have an API available we offer bespoke integrations, such as hosting a webhook - for examples see the section on bespoke integration options.

 

Batch Data Integration

Irregular

For provisions of large datasets (e.g. an initial set of historic data), Anthem’s standard pattern is to enable client’s to upload via Azure Storage Explorer {GUI}.

Other options are:

• AzCopy

• Pulling data from client environment (e.g. from S3 bucket)

• SFTP can be made available on request

 

Regular

Regular data provision is handled via API.

 

Upload

Request

 

 

Request Headers

 

Body

Binary multipart form data

 

Response

 

Example

POST /api/upload/2021-01-01/spins_01.csv?code=ABC123Z== HTTP/1.1 
Host: https://casinomagic-fane01.azurewebsites.net 
Content-Length: 198 
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW

----WebKitFormBoundary7MA4YWxkTrZu0gW 
Content-Disposition: form-data; name=""; filename="spins_01.csv" 
Content-Type: text/csv (data) ----WebKitFormBoundary7MA4YWxkTrZu0gW

curl --location --request POST 'https://casinomagic-fane01.azurewebsites.net/api/upload/2021-01- 
01/spins01.csv?code=ABC123Z==' \ 
--form '=@"/path/to/file/spins-048046c6b0cf-c000.csv"'

 

Real-Time Data

Sending Events to Anthem

Future Anthem can ingest real-time data directly from client systems via a bespoke connection.

Future Anthem has successfully integrated clients via a direct connection to: 

• Client Kafka brokers to consume real-time feeds from Kafka 
• Client RabbitMQ brokers 
• Various databases and DWH implementations to consume real-time feeds via change data capture. Examples include Postgres and Snowflake

 

Anthem’s bespoke connectors support: 

• Static IPs for IP whitelisting 
• SSL with self-signed certificates 
• Authentication via username and password or via certificates

 

Receive Events from Anthem

• Clients can receive real-time data from Future Anthem’s real-time engine without providing an API

• Clients can connect to Future Anthem’s systems to poll data directly via a bespoke connection

 

Future Anthem supports:

• Hosting a client webhook

• Providing a message broker to connect to e.g. Kafka or AMQP

• Static IPs for IP whitelisting

• Authentication via username and password or certificates

 

Batch Data

Providing files to Anthem

Future Anthem can ingest files with batch data directly from client file servers or blob storage, and can also host a file server or blob storage on a client’s behalf.

Future Anthem has successfully integrated clients via:

• SFTP
• Blob storage in Azure and AWS S3
• Ingestion on-time schedules
• Ingestion triggered by notifications
  
  

Future Anthem can deliver files directly to client systems using a wide range of bespoke integration options.

 

Future Anthem supports:

• SFTP
• Blob Storage in all major cloud providers such as Azure and AWS S3
• Uploading data via client-hosted APIs