Integrations for the pixPLace API
Pick the tool you already use. Every recipe is a working example with the exact request, the headers, the retry rule and the errors you will meet. All of them call the same public API, described in one file: the OpenAPI spec.
Choose your tool
curl
For whom
Anyone who wants to try the API in a terminal first, or call it from a shell script or a cron job.Publish a post with an image: the server downloads the image from a public URL, then the post is created with the stored copy.
Open the recipePython (requests)
For whom
Developers and data people who already have content in Python and want it published on a schedule.Publish one post per run from a cron job or a task scheduler, with safe retries.
Open the recipeJavaScript / Node.js (fetch)
For whom
Web developers who want to publish from a Node.js script, a serverless function or a build step.Publish a post with an image from code: upload by URL first, then create the post.
Open the recipeChatGPT Custom GPT Actions
For whom
ChatGPT users who build a Custom GPT that works with their own pixPLace account.Read the new comments under your posts and answer them from the chat, one reply at a time, after you approve the text.
Open the recipeClaude and OpenAI function calling
For whom
Developers who build an agent with the Claude API or the OpenAI API and want it to use pixPLace as a tool.An agent that uploads media, publishes posts, reads the comment inbox and replies, through tools that come straight from the spec.
Open the recipeZapier (Webhooks by Zapier)
For whom
No-code users who already collect content in a Zapier trigger such as a new row, a new RSS item or a new file.Publish a post every time the trigger fires: upload the image from its URL, then create the post.
Open the recipeMake (HTTP module)
For whom
No-code users who build scenarios in Make and keep their content in Airtable, a spreadsheet or a form.Publish a post for every new item of the scenario: upload the image by URL, then create the post.
Open the recipen8n (HTTP Request node)
For whom
Self-hosters and automation builders who run workflows in n8n.Publish a post for every item the workflow produces: upload the image by URL, then create the post.
Open the recipePipedream (Node.js code step)
For whom
People who run workflows in Pipedream and want their pixPLace numbers in Slack, a sheet or an email.Read the growth of your account per day (posts, likes, comments, new followers) every morning and pass the series to the next step.
Open the recipeTelegram bot
For whom
Creators who want a message in Telegram when someone comments under their posts.Poll the comment inbox every few minutes and forward each new comment to a Telegram chat.
Open the recipeGitHub Actions
For whom
Developers and teams who already keep content or a release process in a GitHub repository.Publish a post on a schedule or after a release: upload the image by URL, then create the post.
Open the recipeGoogle Sheets (Apps Script)
For whom
Content managers who plan posts in a spreadsheet and want to publish them without leaving it.Publish every row that has no status yet: upload its image by URL, create the post and write the post address into the sheet.
Open the recipe
Before you start
- Create a key in Settings → Developer. One key acts for one account, and it is shown once.
- Send it as
Authorization: Bearer ppk_live_XXXXXXXXon every request except the two public lists. - Send an
Idempotency-Keywhen you create a post, a story or an upload, and reuse it when you retry. - On 429 and 503 wait the seconds in
Retry-After. Limits, error codes and every endpoint are on the developer guide.