curl -X GET https://api3.waved.co/api/v1/data/venue/trending \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer YOUR-TOKEN' \
-d '{ }'
This endpoint returns data of how the venue is trending.
The data shows the movement of the mood index and loudness index over the last 6 hours.
The data is updated every 15 minutes and is useful for understanding the trend of the venue, and to act on the crowd behavior.
It also includes a summary of the trend, which is a destilled version of the trend, indicating if its trending up, down or stable.
Note that when using data on a venue basis its important to understand that the data is an average of all zones in the venue, and that the average can be misleading if the venue has zones with very different behavior.
This is why all /venue endpoints include a "representative" index that is calculated only from the 30% - 50% (size dependant) busiest zones in the venue.
Which data type to use, venue average, venue representative or zone data, depends on the venue and the solution being created.
{ "trending": { "mood": { "average": { "index": "<number[]>", "tag": "<string[]>" }, "representative": { "index": "<number[]>", "tag": "<string[]>" } }, "loudness": { "average": { "index": "<number[]>", "tag": "<string[]>" }, "representative": { "index": "<number[]>", "tag": "<string[]>" } }, "time": { "utc0": "<string[]>", "venue_local": "<string[]>" } }, "summary": { "average": { "mood": { "index": "-1 | 0 | 1", "tag": "<string>", "speed_tag": "<string>", "rate_per_hour": "<number>", "synopsis": "<string>" }, "loudness": { "index": "-1 | 0 | 1", "tag": "<string>", "speed_tag": "<string>", "rate_per_hour": "<number>", "synopsis": "<string>" } }, "representative": { "mood": { "index": "-1 | 0 | 1", "tag": "<string>", "speed_tag": "<string>", "rate_per_hour": "<number>", "synopsis": "<string>" }, "loudness": { "index": "-1 | 0 | 1", "tag": "<string>", "speed_tag": "<string>", "rate_per_hour": "<number>", "synopsis": "<string>" } } } }