Pinterest API (Trial → Standard). Any success stories / tips for Standard access approval?

Questions
, , ,
1

Context / What I’m trying to build

Hi n8n community! I’m building an automation workflow in n8n to generate and publish Pinterest Pins for a small ecommerce brand.

Goal (end-to-end):

  1. Take product info (SKU / product URL / key features / style tags)

  2. Use LLM to generate: image prompt + Title + Description + keywords/tags + board mapping

  3. Generate image (AI image or provided product image)

  4. Publish a Pin via Pinterest API (image + title/description + link + board)

  5. Save everything into a “ready-to-publish” database (Notion/Sheet) + mark status

Progress (current blockers):

  • n8n has no native Pinterest credential, so I’m using HTTP Request + Generic OAuth2.

  • My Pinterest app is approved for Trial access (I have Client ID), but I’m blocked from getting the App Secret until I upgrade to Standard access.

  • Pinterest requires a video demo (OAuth flow + main Pinterest actions) to upgrade from Trial → Standard.

bddb238baaed0303bc1e26ac043107d8
bddb238baaed0303bc1e26ac043107d8988×1204 157 KB

Question:
Has anyone successfully built a similar “generate + publish Pin” workflow in n8n and gotten Standard access approved? Any tips on:

  • What the minimum acceptable demo video looks like (OAuth + create pin / boards)?

  • Common gotchas where GET works but POST /v5/pins fails (e.g. “Authorization failed”), even in sandbox?

2

Hi @Michelle_Jiang

According to Pinterest’s API documentation, Standard access requires a video demo showing:

  1. OAuth authentication flow (Pinterest consent screen)
  2. At least one core action, such as creating a Pin (POST /v5/pins)
  • Image (media_source)
  • Title/description
  • Link
  • Board

Trial access commonly allows GET endpoints, but POST endpoints (like /v5/pins) are restricted until Standard access is approved.

Approval tips (per Pinterest policy):

  • Keep the demo simple
  • Show a legitimate business use case
  • Avoid mass-posting or spam behavior

Once approved, Generic OAuth2 + HTTP Request in n8n works as expected.