Trending sounds API | All Them APIs

What to build with it

Choose a platform and a consistent usage window.
Sort using the documented metric rather than mixing lifetime usage with recent adoption.
Read a shortlisted sound's history and example videos before recommending it.

Provider reference: Virlo documentation. Authentication uses a provider-issued Bearer token, stored on your server.

Endpoints and inputs

1 documented operation. Query and path fields are listed separately from JSON request-body fields.

GET/v1/sounds/trending

Path and query parameters

platform: string (query) · optional · values: tiktok, youtube, instagram
limit: number (query) · optional · default: 20 · minimum: 1 · maximum: 100
page: number (query) · optional · default: 1 · minimum: 1
sort: string (query) · optional · values: videos_7d, videos_30d, usage_count, video_count · default: "videos_7d"
commerce_only: boolean (query) · optional

Documented response fields

data: array · required
data[].id: string · required
data[].external_id: string | null · optional
data[].title: string · required
data[].platform: string · required · values: tiktok, youtube, instagram
data[].duration: number | null · optional
data[].cover_url: string | null · optional
data[].owner_handle: string | null · optional
data[].owner_nickname: string | null · optional
data[].is_original: boolean | null · optional
data[].is_commerce_music: boolean | null · optional
data[].usage_count: number | null · optional
data[].video_count: number · required
data[].avg_views: number · required
data[].videos_in_window: number | null · optional
pagination: object · required
pagination.page: number · required
pagination.limit: number · required
pagination.total: number | null · required
pagination.total_pages: number | null · required
pagination.has_next_page: boolean · required
pagination.has_prev_page: boolean · required
sort: string · optional

Documented HTTP responses: 200, 401, 429. Handle each non-success response explicitly; do not silently convert a failed lookup to an empty result.

Before you integrate

A sound's usage count does not establish audio licensing or suitability for a business account.

Check the provider's current price, allowed use and retention terms before sending requests. An optional field can be absent; the schema alone does not establish its completeness or accuracy.

Give this task to your coding agent

trending-sounds-api agent prompt

Help me implement trending sounds api using the documented Virlo API.

Reference: https://allthemapis.com/social-media-apis/trending-sounds-api
Provider documentation: https://dev.virlo.ai/docs/sounds
Base URL: https://api.virlo.ai
Starting operation: GET /v1/sounds/trending

Read the current provider docs and confirm the required inputs before writing code. Load VIRLO_API_KEY from a server-side environment variable and use Bearer authentication. Do not put the key in client code, logs, analytics, or the chat.

Ask me for any missing video URL, creator handle, research intent, or job ID. Do not invent a result. Ask for approval before starting billable lookups, recurring jobs, or destructive changes. For jobs, keep the returned ID and poll with the documented delay instead of starting the job twice. Handle pagination, rate limits, partial results, and missing fields explicitly.

Build the smallest integration for this task:
1. Choose a platform and a consistent usage window.
2. Sort using the documented metric rather than mixing lifetime usage with recent adoption.
3. Read a shortlisted sound's history and example videos before recommending it.

Return the code, the environment variables I need, and a short explanation of what was actually retrieved versus inferred. Do not execute paid requests until I approve.

Sources and review dates

Virlo's public documentation and OpenAPI schema reviewed October 27, 2026. Endpoint paths and field names below refer to that provider's API. This is an integration reference, not a measured performance ranking.

Corrections: email faizank@docsalot.dev with an official source.