The right board
Make the content’s destination explicit throughout preparation and review.
Give the creative a focused review flow while keeping account access and publishing requirements clear.
Fans APIPlan your visual-content workspace | PinterestConfirm boards, Pins and access |
|---|---|
Destination boardShow where the proposed Pin belongs while the content takes shape. | Destination boardConfirm access to the intended board and the required permissions. |
CreativeReview the image, title and description together. | CreativeCheck the media and field requirements for the selected operation. |
Outbound linkKeep the destination close to the visual preview. | Outbound linkUse a valid destination that complies with applicable platform requirements. |
SubmissionDistinguish a Pin draft from a confirmed result. | SubmissionInspect the documented response instead of assuming publishing succeeded. |
Pinterest availability through FansAPI has not been confirmed. The workflow and illustration are frontend concepts.
A visual workflow with the right context at each step.
Start with the account and board that fit the content. Confirm access before designing a publishing action.
Place the image, title and destination together. Keep the preview visible while the description takes shape.
Review the board, creative and link as one unit. Treat submission and its actual response as separate steps.
A Pin preview with its board and destination kept close at hand.
Make the content’s destination explicit throughout preparation and review.
Keep the image central instead of reducing the content to a row of metadata.
Refine the title and description while the visual remains in view.
Review the link with the content so the next step matches the Pin’s story.
Bring the account, board and proposed content together before an action.
Keep credentials private and confirm read and write permissions separately.
const response = await fetch(process.env.PINTEREST_API_URL, {
headers: {
[process.env.PINTEREST_AUTH_HEADER_NAME]:
process.env.PINTEREST_AUTH_HEADER_VALUE
}
});
const data = await response.json();
console.log(data);import os
import requests
response = requests.get(
os.environ["PINTEREST_API_URL"],
headers={
os.environ["PINTEREST_AUTH_HEADER_NAME"]:
os.environ["PINTEREST_AUTH_HEADER_VALUE"]
},
timeout=30,
)
print(response.json())<?php
$request = curl_init(getenv('PINTEREST_API_URL'));
curl_setopt_array($request, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTPHEADER => [
getenv('PINTEREST_AUTH_HEADER_NAME') . ': ' .
getenv('PINTEREST_AUTH_HEADER_VALUE'),
],
]);
$response = curl_exec($request);
curl_close($request);
echo $response;require "net/http"
require "json"
uri = URI(ENV.fetch("PINTEREST_API_URL"))
request = Net::HTTP::Get.new(uri)
request[ENV.fetch("PINTEREST_AUTH_HEADER_NAME")] =
ENV.fetch("PINTEREST_AUTH_HEADER_VALUE")
response = Net::HTTP.start(uri.host, uri.port,
use_ssl: uri.scheme == "https", read_timeout: 30
) { |http| http.request(request) }
puts JSON.parse(response.body)var request = HttpRequest.newBuilder()
.uri(URI.create(System.getenv("PINTEREST_API_URL")))
.header(
System.getenv("PINTEREST_AUTH_HEADER_NAME"),
System.getenv("PINTEREST_AUTH_HEADER_VALUE"))
.timeout(Duration.ofSeconds(30))
.GET().build();
var response = HttpClient.newHttpClient()
.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());curl --fail-with-body --max-time 30 \
"$PINTEREST_API_URL" \
-H "$PINTEREST_AUTH_HEADER_NAME: $PINTEREST_AUTH_HEADER_VALUE"PINTEREST_API_URL · server environmentKeep the important details visible without crowding the image.
| Element | In the preview | What to check |
|---|---|---|
| Board | Content destination | The selected board and the account that can access it. |
| Media | Visual preview | The image and media requirements of the confirmed operation. |
| Copy | Title & description | The text that gives the visual its meaning. |
| Link | Next destination | The intended URL, reviewed before submission. |
The illustration shows a draft composition. No Pin is created by this page.
Prepare the account and permissions your Pinterest workflow needs. Confirm the FansAPI connection separately.
Identify the account, board and operation your application needs to work with.
Pinterest documents OAuth and resource scopes. Confirm the access method and operations available through FansAPI.
Check the creative, destination and media requirements against the final integration contract.
The essentials before your first request.