REST API · Ad accounts
List instagram accounts
The Instagram accounts an ad of a Facebook page can run with
GEThttps://api.apogee.ad/api/v1/pages/{page}/instagram-accounts
What it does
With ad_account_id: the page's own first, then the ones assigned to that ad account in Business Settings, the one a launch uses marked recommended (a page without its own Instagram account runs with the ad account's). Without it: the page's linked account only.
Request
GET /pages/{page}/instagram-accounts on https://api.apogee.ad/api/v1.
Path parameters
-
pagestring path requiredFacebook page id
Query parameters
-
limitinteger query optionalPage size
-
cursorstring query optionalnext_cursor of the previous page
-
ad_account_idstring query optionalMeta ad account id (act_…)
Headers
-
Authorizationstring header requiredBearer apk_…: an API key with the scope of this route.
Response
200. A page of results: pass next_cursor as cursor for the next one, limit from 1 to 200 (default 50).
-
dataarray of objectsFields of each item (5)
-
idstring -
usernamestring or null -
namestring or null -
linkedboolean -
recommendedboolean
-
-
has_moreboolean -
next_cursorstring or null
Every answer carries X-Request-Id (give it to support), Apogee-Version: 2026-10-06, and the RateLimit and RateLimit-Policy headers.
Errors
Errors are application/problem+json with a stable code to switch on (all the codes).
| Status | Possible codes |
|---|---|
| 400 Bad request | idempotency_key_required, not_supported, request_refused, validation_failed |
| 401 Unauthorized | invalid_api_key |
| 403 Forbidden | account_not_connected, forbidden, insufficient_scope, meta_permission_denied, platform_permission_denied, upgrade_required |
| 404 Not found | not_found |
| 412 Precondition failed | drive_not_connected, meta_not_connected, platform_not_connected |
| 429 Too many requests | daily_read_cap, meta_rate_limited, platform_rate_limited, quota_exceeded, rate_limited |
| 500 Internal server error | internal_error |
| 502 Bad gateway | drive_error, launch_failed, meta_error, platform_error, upstream_error |
Example
With your key in APOGEE_API_KEY (create one):
curl 'https://api.apogee.ad/api/v1/pages/100000000000001/instagram-accounts' \
-H "Authorization: Bearer $APOGEE_API_KEY"{
"data": [
{
"id": "120200000000000001",
"username": "nordlicht.official",
"name": "Nordlicht | Spring launch",
"linked": false,
"recommended": false
}
],
"has_more": false,
"next_cursor": null
}Access and cost
| Plans | Pro and Scale. |
|---|---|
| Scope | read (scopes). |
| Credits | Free up to the daily free reads (5,000 a day on Pro, 10,000 on Scale), then 1 credit per read. A request that fails costs nothing, a replayed one neither (credits). |
| Rate limit | Read: 600 per 15 minutes on Pro, 1,200 on Scale (rate limits). |
| Meta budget | Reads Meta: spends 1 unit of the account's Meta budget (1,800 per 15 minutes, 900 per ad account). |
| Daily cap | Counts 1 unit toward the 2,000 units one API key can use in 24 hours. |
In the MCP
An AI assistant does the same with this tool of the MCP server:
list_instagram_accounts: The Instagram account linked to a page.
Related operations
- List ad accounts:
GET /ad-accounts - List pages:
GET /ad-accounts/{acc}/pages - List pixels:
GET /ad-accounts/{acc}/pixels - Get pixel events:
GET /ad-accounts/{acc}/pixels/{pixel}/events - List catalogs:
GET /ad-accounts/{acc}/catalogs - List product sets:
GET /catalogs/{id}/product-sets - List custom audiences:
GET /ad-accounts/{acc}/custom-audiences - List templates:
GET /ad-accounts/{acc}/templates - List naming conventions:
GET /ad-accounts/{acc}/naming-conventions - List lead forms:
GET /pages/{page}/lead-forms - List partnership creators:
GET /pages/{page}/partnership-creators - List ad posts:
GET /ad-accounts/{acc}/posts - List page posts:
GET /pages/{page}/posts - Search targeting:
GET /targeting/search - List targeting options:
GET /ad-accounts/{acc}/targeting-options