This relates to the play log end points as noted in the documentation. The logging endpoints are only applicable where Tuned Global is responsible for generating reports on the behalf of a client. If a client is managing their reports internally, then the endpoint (and basic http auth) isn't required.
This model uses a simple challenge and response mechanism with which a server can request authentication information (Username and password) from a client.
The client passes the authentication information to the server in an Authorization header e.g. Authorization: Basic <credentials>, where <credentials> is the Base64 encoding of Username and password joined by a single colon;
Note: Please include the API Key under the ‘StoreId: TestKey’ http header with Basic HTTP Authentication.
Examples
Following are the usage examples from the curl and postman.
curl --location '' --header 'StoreId: TestAPIKey' --header 'Content-Type: application/json' --header 'Authorization: Basic VGVzdEFjY2Vzc0tleUZyb21URzpUZXN0U2VjcmV0S2V5RnJvbVRH' --data '{
"UserId": 0,
"TrackId": 0,
"Country": "string",
"LogPlayType": "Start",
"Seconds": 0,
"Source": "Queue",
"PlayType": "Stream",
"SourceId": 0,
"UserIp": "string",
"DeviceId": 0,
"SubId": 0,
"Guid": "string",
"AudioQuality": "low",
"ExternalPlanId": "string"
}'
'https://api-delivery-connect.tunedglobal.com/api/v5/play/logplay'
