Changes from regular integration

The changes from the regular integration are around the token creation and an additional query parameter when making a request to the streaming API.

These changes apply to the Streaming API endpoint only.

1 - Define the location of the end user using a "location" parameter in the request

We trust that you have the relevant Geo-location technology (e.g GeoComply) within your applications and that you know where your end users are within the US and Canada at the time they access the stream. You then tell us this information in the "location" query parameter in the API request, and we use this information to apply geo-restrictions.

2 - Token creation requires additional parameters to be passed inside the authentication token

This to increase security on our API. If we are allowing customers to define the location of the end users, we must ensure it is not easy for end users or malicious actors to grab Streaming API requests and easily bypass geo-restrictions.

Timestamp, request URL, API secret and location info are all hashed into the authentication token (see Token Creation section).

3 - Token is created using a HMAC SHA256 hash

Rather than an HMAC MD5 hash, this token uses HMAC SHA256.

There are no changes to the other endpoints that you need to call, or the responses that are returned. Those remain as described in https://docs.imgarena.com/streaming-integration/