SDKs
How to integrate with PostMantis today using raw HTTP, OpenAPI, and thin wrappers.
HTTP-first by design
PostMantis is HTTP-first and OpenAPI-first. Official SDKs can come later, but the public HTTP contract and OpenAPI document are still the source of truth.
Canonical integration surfaces
Public HTTP API
The runtime contract for profiles, posts, uploads, and publish lifecycle reads.
OpenAPI document
Use `/api/openapi-docs` as the schema source for generated clients.
Generated API reference
Browse the live reference under [API Reference](/docs/api/overview).
Official SDKs
PostMantis does not currently publish official language SDKs.
That is intentional for this phase. The OpenAPI document is the stable source for generated clients and thin wrappers.
Recommended approach
Use raw HTTP
Best when you want the most direct and explicit control over runtime behavior.
Generate a client from OpenAPI
Best when your team prefers typed clients or generated wrappers.
Keep wrappers thin
SDKs and MCP layers should preserve the public API semantics instead of inventing a new contract.
Use raw HTTP
const response = await fetch("https://postmantis.com/api/posts", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.POSTMANTIS_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
post: {
body: "The launch is live.",
},
profiles: ["4339a6bc-9cd3-455e-8f91-df8bc63f12d7"],
}),
});Generate a client from OpenAPI
If your team prefers typed clients, generate them from /api/openapi-docs.
A good wrapper should make auth and request typing easier without hiding these product truths:
POST /api/postsaccepts work and returns an initial statePOST /api/posts/{id}/publishaccepts work and returns an initial state- final delivery outcomes belong on post readbacks
- API key scope still controls what the client can read and write
Where skills and templates fit
Skills and templates are useful when an AI client needs reusable instructions, but they should still sit on top of MCP or HTTP.
A clean layering looks like this:
- PostMantis behavior lives in HTTP, OpenAPI, MCP,
- generated clients and thin SDKs help with developer ergonomics
- skills and templates help an AI client use those surfaces correctly
Notes for wrapper authors
- keep field names aligned with the HTTP API
- keep status semantics aligned with the HTTP API
- do not pretend publish is synchronous
- do not hide key scope or permission failures
- link back to the real API and MCP docs instead of duplicating every detail in the wrapper