| Drawio | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Time-Based or Offset-Based Request Pattern:
Most APIs allow time-based access where we can specify a time-period to load data.
However, some APIs also allow an offset-based request, where each data returned is associated with a offset-id. Offsets are ordered Integers/Longs, which bring data in order. In those APIs, we can ask the API to give us new data by sending the offset with the request. Any data newer than the offset is returned.
We need to know what request pattern your API has.
Append-Only (nice to have): Ideally, your data is append-only. This means, that no historic data is changed, and all changes are made going forward. Some systems a call this approach “event based”, where each event describes a change at a specific time.
Late arrivals: If your API is not based on events, and your data also changes historically, we need to know a limitation time-frame how long changes can happen for past objects. For example, if yo allow data to change until 30 days in the past, we support this.
iGaming Data Models
When your business model is from iGaming, we will require you to help us mapping your data to our unified iGaming data model. We have two models where columns are prepared for you to map your data.
Please look at this Spreadsheet for further details: https://docs.google.com/spreadsheets/d/1UaKHjVxgsJw5w4TCZOYlvsQamEYxSpiVZ0GlFdwPW24/edit?usp=sharing