Get Instagram audio metadata
Fetch one audio asset's metadata by ID. Use it to re-validate a stored
audioId before a scheduled Reel publishes, or to refresh the preview
downloadUrl (Meta expires preview URLs after roughly 1.5 days).
Same connection requirement as the search endpoint: Facebook-Login Instagram accounts only.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
The ID of the Instagram account
Instagram audio asset ID
^\d{1,30}$Response Body
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.instagram.getInstagramAudio({ path: { accountId: 'account_abc123', audioId: 'audio_abc123', },});console.log(data);{
"audio": {
"audioId": "482851939985510",
"title": "string",
"audioType": "music",
"durationInMs": 0,
"displayArtist": "string",
"coverArtworkThumbnailUrl": "string",
"downloadUrl": "string",
"igUsername": "string",
"profilePictureUrl": "string",
"isAdsEligible": true,
"onPlatformAudioPreviewLink": "string"
}
}{
"error": "string",
"type": "invalid_request_error",
"code": "string",
"param": "string",
"platform": "string",
"platformError": {},
"details": {}
}{
"error": "Unauthorized"
}Search Instagram audio GET
Search Instagram's audio catalog (licensed music or original sounds), or list what is currently trending by omitting `q`. Returns up to ~30 assets; Meta exposes no pagination on this edge. Pass the returned `audioId` as `platformSpecificData.audioConfiguration.audioId` when creating a Reel to publish it with that track. Requires an Instagram account connected via **Facebook Login**. Meta hosts this catalog on graph.facebook.com only, so accounts connected with classic Instagram Login receive a 400 (`instagram_audio_requires_facebook_login`) and must be reconnected choosing the Facebook option.
Get Instagram publishing limit GET
Returns the account's remaining content-publishing quota for Instagram's rolling 24-hour window, so you can pace publishing and warn before the cap is reached. `quotaUsage` counts containers published since the start of the window. Always compare against the returned `quotaTotal` rather than hardcoding a number: Meta's prose documentation and the live API disagree on the value, and the live value is authoritative.