> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adside.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Account-pages get

> List the Facebook Pages usable for ads on the given ad account: every Page the person who connected Meta can advertise with (ads access on the Page is what Meta checks), with already_used_by_this_ad_account on the ones the account has run ads with. A listed Page is ready to use as page_id in promoted_object and object_story_spec: Meta has no step that assigns a Page to an ad account, so never ask the user to add, assign or reconnect a listed Page. default_page_id is the Page to use when the user has not named one; it is null when they must choose (default_page_reason says why). instagram_account_id is the Page's Instagram business account; pass it as create_ad_creative's instagram_actor_id so the ad runs under the brand's own Instagram account. A missing instagram_account_id does NOT mean the Page has no Instagram account (usually it is not connected to the ad account yet). The response's note says what to ask when no Page is usable or the choice is ambiguous.

CLI: `adside meta account-pages get`



## OpenAPI

````yaml /api-reference/openapi.yaml post /v1/workspaces/{workspaceId}/meta/account-pages/get
openapi: 3.1.0
info:
  title: Adside API
  version: 1.0.0
  description: >-
    Campaigns, creatives, assets and reporting across your ad accounts. Call it
    with a personal API key as a bearer token, or with the `adside` CLI: each
    page names its command.
servers:
  - url: https://api.adside.ai
    description: Production
security:
  - userAccess: []
tags:
  - name: Account
  - name: Reporting
  - name: Meta
  - name: Google Ads
  - name: LinkedIn
  - name: TikTok
  - name: Reddit
  - name: Snapchat
  - name: X
  - name: Google Tag Manager
  - name: Creatives
  - name: Creative styles
  - name: Media
  - name: Characters
  - name: Assets
  - name: Brands
  - name: Brain
  - name: Research
  - name: Boards
  - name: Artifacts
  - name: Audiences
  - name: Ad comments
  - name: Publications
  - name: Routines
  - name: Skills
  - name: To-dos
  - name: Audit
  - name: Credits
paths:
  /v1/workspaces/{workspaceId}/meta/account-pages/get:
    post:
      tags:
        - Meta
      summary: Account-pages get
      description: >-
        List the Facebook Pages usable for ads on the given ad account: every
        Page the person who connected Meta can advertise with (ads access on the
        Page is what Meta checks), with already_used_by_this_ad_account on the
        ones the account has run ads with. A listed Page is ready to use as
        page_id in promoted_object and object_story_spec: Meta has no step that
        assigns a Page to an ad account, so never ask the user to add, assign or
        reconnect a listed Page. default_page_id is the Page to use when the
        user has not named one; it is null when they must choose
        (default_page_reason says why). instagram_account_id is the Page's
        Instagram business account; pass it as create_ad_creative's
        instagram_actor_id so the ad runs under the brand's own Instagram
        account. A missing instagram_account_id does NOT mean the Page has no
        Instagram account (usually it is not connected to the ad account yet).
        The response's note says what to ask when no Page is usable or the
        choice is ambiguous.


        CLI: `adside meta account-pages get`
      operationId: meta.get_account_pages
      parameters:
        - name: workspaceId
          in: path
          required: true
          schema:
            type: string
            minLength: 1
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $schema: https://json-schema.org/draft/2020-12/schema
              type: object
              properties:
                account_id:
                  description: Meta Ad Account ID (uses configured account if not provided)
                  type: string
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $schema: https://json-schema.org/draft/2020-12/schema
      security:
        - userAccess: []
components:
  securitySchemes:
    userAccess:
      type: http
      scheme: bearer
      description: >-
        A personal API key (`adside_pat_…`) or a token from `adside login`.
        Either carries the permissions of the person it belongs to.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.