List ad posts

What it does

Request

GET /ad-accounts/{acc}/posts on https://api.apogee.ad/api/v1.

Path parameters

• acc string path required

  Meta ad account id (act_…)

  Matches ^(act_)?\d{1,32}$

Query parameters

• limit integer query optional

  Page size

  Default 50

  1 to 200

• cursor string query optional

  next_cursor of the previous page

• campaign_id string query optional

  Matches ^\d{1,40}$

Headers

• Authorization string header required

  Bearer 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).

• data array of objects
  Fields of each item (14)

  • object_story_id string or null

    A Facebook post: <pageId>_<postId>

  • instagram_media_id string or null
  • instagram_user_id string or null
  • page_id string or null
  • instagram_permalink string or null
  • permalink string or null
  • message string or null
  • caption string or null
  • created_time string or null
  • thumbnail_url string or null
  • media_type string or null
  • likes number or null
  • comments number or null
  • ads array of objects

    /ad-accounts/{acc}/posts: the ads using this post

    Fields of each item (3)

    • id string
    • name string or null
    • status string or null
• has_more boolean
• next_cursor string 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).

Example

With your key in APOGEE_API_KEY (create one):

curl 'https://api.apogee.ad/api/v1/ad-accounts/act_1234567890/posts' \
  -H "Authorization: Bearer $APOGEE_API_KEY"

{
  "data": [
    {
      "object_story_id": "120200000000000001",
      "instagram_media_id": "120200000000000001",
      "instagram_user_id": "17840000000000001",
      "page_id": "100000000000001",
      "instagram_permalink": "https://www.example.com/products/nordlicht-jacket",
      "permalink": "https://www.example.com/products/nordlicht-jacket",
      "message": "Thanks for your message! Our team answers you in a private message.",
      "caption": "Example text",
      "created_time": "09:00",
      "thumbnail_url": "https://www.example.com/products/nordlicht-jacket",
      "media_type": "120200000000000001",
      "likes": 1,
      "comments": 1,
      "ads": [
        {
          "id": "120200000000000001",
          "name": "Nordlicht | Spring launch",
          "status": "ACTIVE"
        }
      ]
    }
  ],
  "has_more": false,
  "next_cursor": null
}

Access and cost

In the MCP

An AI assistant does the same with this tool of the MCP server:

• list_posts: Existing posts a new ad can reuse with their likes and comments: the posts behind your ads, a page's posts, or its Instagram posts.

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 instagram accounts: GET /pages/{page}/instagram-accounts
• List lead forms: GET /pages/{page}/lead-forms
• List partnership creators: GET /pages/{page}/partnership-creators
• List page posts: GET /pages/{page}/posts
• Search targeting: GET /targeting/search
• List targeting options: GET /ad-accounts/{acc}/targeting-options