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

# List the Pinterest boards of every Pinterest account

> The boards of every connected Pinterest account of the workspace, each with the account that owns it. For a picker that cannot pass an account, such as a Make field; otherwise use GET /v1/accounts/{id}/pinterest/boards. Post to a board from its own account. An account whose boards cannot be read is listed in `meta.errors`, and the boards of the other accounts are still returned.



## OpenAPI

````yaml /openapi.json get /v1/accounts/pinterest/boards
openapi: 3.0.0
info:
  title: Social media studio API
  description: >-
    The Social media studio API lets you programmatically manage your social
    media workflow — create and schedule posts, organize media, track analytics,
    manage your team, and more.


    ## Base URL


    ```

    https://api.so-me.studio

    ```


    ## Authentication


    All `/v1/*` endpoints require an API key passed via the `X-API-Key` header.


    ```

    X-API-Key: sk_live_xxxxxxxxxxxxxxxxxxxxxxxx

    ```


    ## Scopes


    A key has full access unless you give it scopes when you create it. A scoped
    key can call only the endpoints its scopes cover; other endpoints return
    `403 Forbidden`. A `GET` endpoint needs `<resource>:read`; `POST`, `PUT`,
    `PATCH` and `DELETE` need `<resource>:write`, which includes `read`.
    Resources: `accounts`, `posts` (also drafts and approvals), `media`,
    `analytics` (read only), `inbox`, `ai`, `biolinks`, `teams`, `settings`,
    `webhooks`, `support`, `templates` (read only), `whatsapp`. The API key and
    workspace endpoints under `/v1/settings`, and `PATCH /v1/settings/profile`,
    need a full-access key. Scoped keys cannot use the MCP server.


    ## Getting your API key


    1. Log in to your workspace at [Social media studio](https://so-me.studio)

    2. Go to **Settings** > **API** tab

    3. Click **New API Key**, give it a name, and copy the key


    > The full key is shown only once. Store it securely.


    ## Rate limits


    60 requests per minute per workspace. If you exceed this, you'll receive a
    `429 Too Many Requests` response.


    ## Plans


    API access is available on the **Standard**, **Advanced**, and **Lifetime**
    plans.
  version: '1.0'
  contact: {}
servers:
  - url: https://api.so-me.studio
    description: Production
security: []
tags:
  - name: Posts
    description: Create, manage, schedule, and publish social media posts
  - name: Accounts
    description: Manage connected social media accounts
  - name: Drafts
    description: Create and manage draft posts
  - name: Media
    description: Upload, organize, and manage media files and folders
  - name: Analytics
    description: Platform and post-level analytics across social accounts
  - name: Inbox
    description: Social inbox conversations, replies, and saved replies
  - name: AI
    description: AI-powered text and image generation
  - name: Approvals
    description: Post approval workflow for team collaboration
  - name: Teams
    description: Team member and invitation management
  - name: Biolinks
    description: Bio link pages with buttons, posts, and themes
  - name: Settings
    description: Profile, organization, API keys, billing, and usage
  - name: Authentication
    description: Register, login, password reset, and device authorization
  - name: Plans
    description: Available subscription plans, features, and addons
  - name: Public Biolink
    description: Public biolink page resolution and analytics tracking (no auth required)
paths:
  /v1/accounts/pinterest/boards:
    get:
      tags:
        - Accounts
      summary: List the Pinterest boards of every Pinterest account
      description: >-
        The boards of every connected Pinterest account of the workspace, each
        with the account that owns it. For a picker that cannot pass an account,
        such as a Make field; otherwise use GET
        /v1/accounts/{id}/pinterest/boards. Post to a board from its own
        account. An account whose boards cannot be read is listed in
        `meta.errors`, and the boards of the other accounts are still returned.
      operationId: V1AccountsController_workspacePinterestBoards
      parameters: []
      responses:
        '200':
          description: The boards of every Pinterest account
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1WorkspacePinterestBoardsDto'
      security:
        - X-API-Key: []
components:
  schemas:
    V1WorkspacePinterestBoardsDto:
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/V1WorkspacePinterestBoardDto'
        meta:
          $ref: '#/components/schemas/V1WorkspacePinterestBoardsMetaDto'
      required:
        - data
        - meta
    V1WorkspacePinterestBoardDto:
      type: object
      properties:
        id:
          type: string
          description: >-
            The board ID. Send it as `metaData.boardId` when you create a
            Pinterest post.
          example: '1234567890123456789'
        name:
          type: string
          description: The board name.
          example: Recipes
        description:
          type: string
          nullable: true
          description: The board description, or null when it has none.
          example: null
        privacy:
          type: string
          description: Who can see the board.
          enum:
            - PUBLIC
            - PROTECTED
            - SECRET
          example: PUBLIC
        accountId:
          type: string
          description: >-
            The UUID of the Pinterest account that owns the board. Post to the
            board from this account.
          example: 11111111-1111-4111-8111-111111111111
        accountName:
          type: string
          description: The name of that Pinterest account.
          example: mybrand
      required:
        - id
        - name
        - description
        - accountId
        - accountName
    V1WorkspacePinterestBoardsMetaDto:
      type: object
      properties:
        total:
          type: number
          description: The number of boards in `data`.
          example: 3
        accounts:
          type: number
          description: The number of connected Pinterest accounts.
          example: 1
        hasMore:
          type: boolean
          description: >-
            True when an account has more boards than Pinterest returns at once
            (250). `data` then holds its first 250.
          example: false
        errors:
          description: >-
            The accounts whose boards could not be read. The boards of the other
            accounts are still in `data`.
          type: array
          items:
            $ref: '#/components/schemas/V1PinterestBoardsErrorDto'
      required:
        - total
        - accounts
        - hasMore
        - errors
    V1PinterestBoardsErrorDto:
      type: object
      properties:
        accountId:
          type: string
          description: The UUID of the Pinterest account.
        message:
          type: string
          description: Why its boards are missing from `data`.
          example: >-
            Pinterest refused access to the boards of this account. Reconnect
            the account.
      required:
        - accountId
        - message
  securitySchemes:
    X-API-Key:
      type: apiKey
      in: header
      name: X-API-Key

````

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