Publishing API

Pinterest publishing API with one SocialClaw workspace.

Start the standard Pinterest OAuth flow from SocialClaw, then inspect board-scoped capabilities and discovery actions from the connected account in the same workspace. SocialClaw supports standard pins, video pins, and multi-image pins for board-centric Pinterest publishing.

Try the CLI Open dashboard

Account type Board-centric Pinterest target Pinterest supports one video or up to five image assets per pin.

Best fit Embedded SaaS Pinterest is board-centric in SocialClaw today.

What SocialClaw supports for this workflow

A quick overview of what this workflow supports.

Account target Board-centric Pinterest target SocialClaw supports standard pins, video pins, and multi-image pins for board-centric Pinterest publishing.

Auth model OAuth Start the standard Pinterest OAuth flow from SocialClaw, then inspect board-scoped capabilities and discovery actions from the connected account in the same workspace.

Media envelope Pinterest supports one video or up to five image assets per pin. Pinterest fetches image URLs, while SocialClaw uploads video when the pin mode requires it.

Inspection Validate, apply, inspect Pin analytics and account analytics are supported through the standard analytics commands after the board target is connected. Pinterest-specific reconciliation is not advertised as a current first-party capability.

What the payload needs

The main fields and constraints to account for.

Board-centric Pinterest target stored in the SocialClaw workspace
Pinterest supports one video or up to five image assets per pin.
Provider-specific settings such as pinMode, link, altText, boardSectionId, coverImageUrl, coverImageKeyFrameTime
Workspace API key auth and post or run inspection after apply

How the workflow runs

Connect the account, validate the post, then publish.

Step 1

Authenticate the workspace

Use the workspace API key with the CLI or hosted HTTP API so the publishing workflow stays attached to the same customer workspace.

Step 2

Connect Pinterest

Start the standard Pinterest OAuth flow from SocialClaw, then inspect board-scoped capabilities and discovery actions from the connected account in the same workspace.

Step 3

Inspect account capabilities and settings

Read the current settings surface, including pinMode, link, altText, boardSectionId, coverImageUrl, coverImageKeyFrameTime, before generating the final payload.

Step 4

Validate before apply

Validation should happen before create-run or apply. Pinterest supports one video or up to five image assets per pin.

Step 5

Inspect the resulting run or post

Pinterest-specific reconciliation is not advertised as a current first-party capability. Pin analytics and account analytics are supported through the standard analytics commands after the board target is connected.

CLI and HTTP examples

Example commands and requests for this route.

CLI flow Pinterest publishing API

socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider pinterest --open
socialclaw accounts capabilities --provider pinterest --json
socialclaw validate -f schedule.json --json
socialclaw apply -f schedule.json --idempotency-key launch_1 --json
socialclaw runs inspect --run-id <run-id> --json

HTTP API flow Hosted SocialClaw endpoints

curl -sS \
  -H "Authorization: Bearer $SC_API_KEY" \
  "https://getsocialclaw.com/v1/keys/validate"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider":"pinterest"}' \
  "https://getsocialclaw.com/v1/connections/start"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d @schedule.json \
  "https://getsocialclaw.com/v1/posts/validate"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d @schedule.json \
  "https://getsocialclaw.com/v1/posts/apply"

Current limitations

A few practical limits to keep in mind.

Pinterest is board-centric in SocialClaw today.
Product, collection, and idea surfaces should be treated as capability-gated or beta rather than assumed for every workspace.
Product pin mode is not available in the generic publish flow without the required Pinterest capability.

Related routes

Related integrations and use cases.

Integration

Pinterest SocialClaw keeps Pinterest connection, board discovery, media handoff, validation, and pin scheduling under one hosted workspace instead of splitting them across separate schedulers and scripts.

Use case

Embedded SaaS Use SocialClaw as the hosted social publishing layer inside another SaaS product while customer account connections stay in one workspace.

Product

Pricing Trial and plan details for CLI or API execution

Product

AI agents overview Main SocialClaw page for AI-agent publishing

Frequently asked questions

What account type does the Pinterest publishing API route use?

Pinterest uses the Board-centric Pinterest target route in SocialClaw. Start the standard Pinterest OAuth flow from SocialClaw, then inspect board-scoped capabilities and discovery actions from the connected account in the same workspace.

What media rules apply to the Pinterest publishing API route?

Pinterest supports one video or up to five image assets per pin. Pinterest fetches image URLs, while SocialClaw uploads video when the pin mode requires it.

What should the workflow inspect before applying Pinterest posts?

Inspect settings such as pinMode, link, altText, boardSectionId, coverImageUrl, coverImageKeyFrameTime and capabilities. Pinterest is board-centric in SocialClaw today.

Run the Pinterest publishing API workflow in SocialClaw

Connect the account once, validate before publish, and keep everything in one workspace.

Try the CLI Open dashboard