postproxy-dev Direct Messages API

1:1 chats and messages

Operations 23

POST /api/posts/{post_id}/comments/{id}/private_reply Private reply to comment #
GET /api/profiles/{profile_id}/chats List chats #
POST /api/profiles/{profile_id}/chats Create or find chat #
GET /api/chats/{id} Get chat #
GET /api/chats/{chat_id}/messages List messages #
POST /api/chats/{chat_id}/messages Send message #
GET /api/messages/{id} Get message #
PATCH /api/messages/{id} Edit message (Telegram only) #
POST /api/messages/{id}/react React to message #
DELETE /api/messages/{id}/unreact Remove reaction #
POST /api/chats/{id}/archive Archive chat (Bluesky only) #
DELETE /api/chats/{id}/archive Unarchive chat (Bluesky only) #
POST /api/chats/{id}/start_typing Show typing indicator (Facebook & Instagram) #
POST /api/chats/{id}/stop_typing Hide typing indicator (Facebook & Instagram) #
POST /api/chats/{id}/pass_thread_control Pass thread control (Facebook & Instagram) #
POST /api/chats/{id}/take_thread_control Take thread control (Facebook, Instagram via Facebook) #
POST /api/chats/{id}/release_thread_control Release thread control (Facebook & Instagram) #
POST /api/chats/{id}/request_thread_control Request thread control (Facebook, Instagram via Facebook) #
GET /api/chats/{id}/thread_owner Get thread owner (Facebook & Instagram) #
GET /api/profiles/{id}/ice_breakers Get ice breakers (Instagram only) #
POST /api/profiles/{id}/ice_breakers Set ice breakers (Instagram only) #
DELETE /api/profiles/{id}/ice_breakers Delete ice breakers (Instagram only) #
POST /api/chats/{id}/mark_read Mark read #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/postproxy-dev:postproxy-dev-direct-messages-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

postproxy-dev-direct-messages-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Postproxy Social Media Direct Messages API
  version: '2026-09-21'
  summary: Unified social media API for publishing, comments, direct messages, and reviews.
  description: 'The Postproxy API lets you programmatically create and manage social media posts across Facebook, Instagram, TikTok, LinkedIn, YouTube, X (Twitter), Threads, Pinterest, Bluesky, Telegram, and Google Business. Beyond publishing you can read and reply to comments, read and send direct messages, and reply to Google Business reviews and Facebook Page recommendations.


    Send one payload; Postproxy maps it to each platform''s rules and returns a per-platform outcome. Sandbox mode is included on all plans for development without real accounts.


    Human-readable reference: https://postproxy.dev/reference/overview/


    ## Versioning and deprecation


    The API has a single stable version served at https://api.postproxy.dev/api. Releases are identified by this document''s date-based `info.version`. Changes are additive: new endpoints, new optional parameters, and new response fields may appear, and clients should ignore fields they do not recognize. Existing fields, parameters, and status codes are not changed or removed without a deprecation cycle.


    When an endpoint or field is deprecated it is marked `deprecated: true` in this specification and announced in the changelog (https://postproxy.dev/getting-started/changelog/) at least 90 days before removal.'
  termsOfService: https://postproxy.dev/terms-conditions/
  contact:
    name: Postproxy Support
    url: https://postproxy.dev/developers/
    email: support@postproxy.dev
  x-versioning:
    strategy: stable-single-version
    spec-version-format: date (YYYY-MM-DD)
    compatibility: additive-only; breaking changes go through a deprecation cycle
    deprecation-signal: 'deprecated: true in this spec, plus a changelog announcement at least 90 days before removal'
    changelog: https://postproxy.dev/getting-started/changelog/
servers:
- url: https://api.postproxy.dev
  description: Production
security:
- bearerAuth: []
tags:


# --- truncated at 32 KB (65 KB total) ---
# Full source: https://artifacts.apis.io/postproxy-dev/openapi/postproxy-dev-direct-messages-api-openapi.yml