Endpoint reference
api/v1/data/venue/live
This endpoint returns live data for the venue.
https://api3.waved.coBearer tokenThe full migrated endpoint description and response example are preserved below. They must be checked against the authoritative API contract before publication.
Migrated reference
The complete public source content is preserved below. Examples still require technical verification before launch.
GET :
api/v1/data/venue/live
cURL
curl -X GET https://api3.waved.co/api/v1/data/venue/live \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer YOUR-TOKEN' \
-d '{ }'About the endpoint
This endpoint returns live data for the venue.
Data fetched on a venue basis is useful but averages are not always the best way to understand the crowd behavior.
For instance, hotels and large restaurants often have quiet lounges or areas and busy bars, and the average of these zones can be misleading.
Therefor each data type, mood, loudness and vibe has a "representative" index that is calculated only from the 30% - 50% (size dependent) busiest zones in the venue. In addition the average index is also returned for each data type.
It's up to the developer to decide if the average or the representative index is the most useful for a given solution or venue. Other alternatives include using the busiest zone from the api/v1/data/zones/busiest endpoint, or a suitable selection of zones from the developers choosing.
Return Object
{
"mood": {
"average": {
"index": "<number>",
"tag": "<string>"
},
"representative": {
"index": "<number>",
"tag": "<string>"
}
},
"loudness": {
"average": {
"index": "<number>",
"tag": "<string>"
},
"representative": {
"index": "<number>",
"tag": "<string>"
}
},
"vibe": {
"average": {
"index": "<number>",
"tag": "<string>"
},
"representative": {
"index": "<number>",
"tag": "<string>"
}
},
"utc0_timestamp": "<string>"
}