Managing multiple Pinterest accounts
Agencies and multi-brand publishers can connect several Pinterest accounts to a single PinBridge project and publish to all of them with one API key. This page explains how many accounts each plan allows and how to keep everything under one roof.
One project, many Pinterest accounts
In PinBridge, an organization contains a project, and you connect one or more Pinterest accounts to that project. Each pin you publish names the account_id it should go out on, so a single API key can drive every connected account.
You do not need a separate PinBridge login per client or per brand. Connect each Pinterest account to the same project, and publish to each by its account_id.
Account limits per plan
The number of Pinterest accounts you can connect is set by your plan:
| Plan | Connected Pinterest accounts |
|---|---|
| Playground (Free) | 1 |
| Starter | 2 |
| Growth | 5 |
| Agency | 15 |
| Enterprise | 50 |
(The plan enum value for Agency is pro; Enterprise is sold as “Custom”.)
Trying to connect one account past your plan limit returns 403 plan_limit with a message naming the limit and your current count. Upgrade the plan to raise the ceiling.
List your connected accounts
curl https://api.pinbridge.io/v1/pinterest/accounts \
-H "X-API-Key: $PINBRIDGE_API_KEY"
Expected response (trimmed):
[
{"id": "6f1c2e4a-3b7d-4c9e-8a21-5d0f9b3e7c41", "username": "brand-one", "status": "active"},
{"id": "0b8e5d27-91f4-4a6c-b3d2-7e1a4c9f6d58", "username": "brand-two", "status": "active"}
]
An API key with no connected accounts returns an empty array [], not a 404, so this is a safe first call to test a key.
Python SDK
from pinbridge_sdk import PinbridgeClient
with PinbridgeClient(api_key="pb_your_api_key") as client:
for account in client.pinterest.list_accounts():
print(account["id"], account["username"])
n8n
Use Connection → List to enumerate accounts, then feed each id into a publish or schedule step as the account. Rate Meter → Get reports the live rate budget per account, which helps you pace publishing across many accounts. See the Node reference.
Consolidate on one account, not many
If you are running several separate PinBridge accounts to get around per-account limits, consolidate them into a single PinBridge account on the right plan instead. High-volume users should connect all of their Pinterest accounts under one PinBridge account on a plan sized for the volume (for example Agency or Enterprise). One account is easier to bill, gives you one place for activity logs and team access, and keeps your rate budget coordinated.
Shared server IPs are expected and safe
Pinterest identifies an account by its OAuth token, not by IP address. PinBridge publishes through shared server IPs, which is exactly what a registered Pinterest API application is expected to do. Using PinBridge alongside other customers on shared IPs is not a risk to your accounts.
Learn more: Is it safe that PinBridge uses shared IPs?.
Watch per-account rate budgets
Each connected account has its own token-bucket rate budget. Check it before a large burst:
curl "https://api.pinbridge.io/v1/rate-meter?account_id=6f1c2e4a-3b7d-4c9e-8a21-5d0f9b3e7c41" \
-H "X-API-Key: $PINBRIDGE_API_KEY"
Note your monthly pin quota is shared across the whole project (it counts successful publishes), while the rate meter is per account. Plan your imports so no single account starves the others.
Next steps
- Team and roles — invite teammates and control who can publish to which accounts.
- Bulk imports (CSV and JSON) — publish to many accounts at once by setting
account_idper row. - Activity logs — see who connected or published on each account.
- PinBridge for n8n — automate multi-account publishing without code.
