Build on 365 Pinterest

Authentication

Every request authenticates with an API key, sent as a Bearer token. Create one in the dashboard — it is shown once, so copy it immediately. Keys are scoped to your account only: they can never see or touch another user's boards or pins. Revoke a key any time from the same page; revoked keys stop working immediately. Keys are app-level, not per Pinterest account: you can connect several Pinterest accounts in the dashboard and switch between them in the sidebar. API calls operate on your active (newest) account by default; pass account_id (query string for GET, body field for POST, tool argument for MCP) to target a specific connected account instead. An unknown account id returns 404.

Authorization: Bearer pk_live_YOUR_KEY_HERE

Rate limit: 60 requests per minute per key. Exceeding it returns HTTP 429 with a Retry-After header. Errors are plain JSON: { "error": "..." }. Base URL for every endpoint below: https://365pinterest.com

REST API reference

Versioned under /api/v1/. Creating a pin never publishes it directly — a future scheduledFor makes it SCHEDULED (the scheduler publishes it at the due time); otherwise it is a DRAFT. Replace pk_live_YOUR_KEY_HERE with your real key, and BOARD_ID / PIN_ID with real ids from the API.

curl https://365pinterest.com/api/v1/account \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE"

curl https://365pinterest.com/api/v1/boards \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE"

curl -X POST https://365pinterest.com/api/v1/boards \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"name": "Weeknight dinners", "description": "Fast recipes for busy evenings", "privacy": "PUBLIC"}'

curl -X POST https://365pinterest.com/api/v1/pins \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"title": "Creamy garlic pasta", "description": "Ready in 20 minutes.", "destinationUrl": "https://example.com/garlic-pasta", "boardId": "BOARD_ID", "imageUrl": "https://example.com/pasta.jpg", "scheduledFor": "2026-11-20T09:00:00Z"}'

curl -X POST https://365pinterest.com/api/v1/pins \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE" \
  -F "title=Creamy garlic pasta" \
  -F "boardId=BOARD_ID" \
  -F "scheduledFor=2026-11-20T09:00:00Z" \
  -F "file=@./pasta.jpg"

curl "https://365pinterest.com/api/v1/pins?status=SCHEDULED&limit=20" \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE"

curl -X POST https://365pinterest.com/api/v1/pins/PIN_ID/schedule \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"scheduledFor": "2026-11-21T09:00:00Z"}'

curl -X POST https://365pinterest.com/api/v1/pins/PIN_ID/cancel \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE"

curl https://365pinterest.com/api/v1/queue \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE"

curl https://365pinterest.com/api/v1/analytics \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE"

WordPress + AI blog

Connect a WordPress site, generate a blog draft with Workers AI, and publish it to WordPress with its Pinterest pin in one call. Writing a draft never publishes it — the draft is saved first, and the publish endpoint posts it. Publishing needs a board and an image to also create the pin; without them the WordPress post still publishes but no pin is made. Replace pk_live_YOUR_KEY_HERE with your real key, and SITE_ID / POST_ID / BOARD_ID with real ids from the API.

curl https://365pinterest.com/api/v1/wordpress/sites \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE"

curl -X POST https://365pinterest.com/api/v1/wordpress/sites \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"siteUrl": "https://example.com", "username": "editor", "appPassword": "abcd EFGH ijkl MNOP"}'

curl -X DELETE https://365pinterest.com/api/v1/wordpress/sites/SITE_ID \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE"

curl "https://365pinterest.com/api/v1/wordpress/blog-posts?limit=20" \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE"

curl -X POST https://365pinterest.com/api/v1/wordpress/blog-posts \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"siteId": "SITE_ID", "topic": "10 weeknight dinners under 30 minutes", "keywords": ["quick dinners", "meal prep"], "tone": "friendly", "length": "medium"}'

curl -X POST https://365pinterest.com/api/v1/wordpress/blog-posts/POST_ID/publish \
  -H "Authorization: Bearer pk_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"boardId": "BOARD_ID", "generateImage": true}'

MCP server

The same features are available to AI clients over the Model Context Protocol, at https://365pinterest.com/mcp (Streamable HTTP, stateless). Authenticate with the same Bearer API key. It works with Claude Desktop, Claude Code, and any standard MCP client.

Claude Desktop

Add this to your Claude Desktop config file (claude_desktop_config.json), replacing the placeholder key with a real one, then restart Claude Desktop.

{
  "mcpServers": {
    "365-pinterest": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://365pinterest.com/mcp",
        "--header",
        "Authorization: Bearer pk_live_YOUR_KEY_HERE"
      ]
    }
  }
}

Claude Code

Run this once in your terminal (replace the placeholder key):

claude mcp add --transport http 365-pinterest https://365pinterest.com/mcp --header "Authorization: Bearer pk_live_YOUR_KEY_HERE"

Available tools

• account_status

  Connection status, username, scopes, board count. Optional account_id.

• list_boards

  List boards (id, name, description, privacy, pin count). Optional account_id.

• create_pin

  Create a draft pin, or a scheduled pin with scheduledFor. Optional account_id.

• schedule_pin

  Schedule an existing draft pin for a future time.

• list_pins

  List pins, filtered by status and/or board. Optional account_id (omit to list across all accounts).

• get_queue

  Up-next scheduled pins, ordered by scheduled time. Optional account_id.

• get_analytics

  Last-30-days totals: impressions, saves, clicks, outbound clicks. Optional account_id.

• wordpress_sites

  List connected WordPress sites. App passwords are never returned.

• connect_wordpress

  Connect a WordPress site with siteUrl, username, and appPassword. Verified against the live WordPress API first.

• write_blog_post

  Generate a blog draft with Workers AI for a connected site. siteId and topic required; keywords, tone, and length optional.

• publish_blog_post

  Publish a draft to WordPress and create its Pinterest pin. postId required; boardId or pinterestBoardId, status, image options, and edited draft fields optional.

• list_blog_posts

  List blog posts, newest first. Optional siteId and limit (default 50, max 100).

Tools return structured JSON. Errors never leak internals — a missing or revoked key returns a JSON-RPC authentication error, and a request over the 60-per-minute limit returns a rate-limit error.