Developer platform
Build on Jestha
The Jestha API lets your service publish Jes, JesClips, and comments on behalf of a Jestha account, and listen for activity via signed webhooks. One HTTP header, no token-exchange dance — designed to be the simplest social API to build against.
Base URL
All API endpoints are served from https://api.jestha.com. Calls against jestha.com (without the api. subdomain) hit the user-facing frontend and will return an HTML 404.
30-second quickstart
Generate a key in Settings → API access, then send it as a Bearer token:
curl -X POST https://api.jestha.com/api/posts \
-H "Authorization: Bearer jes_live_..." \
-H "Content-Type: application/json" \
-d '{"content":"Hello from my service","visibility":"PUBLIC"}'That's it — the response carries the new Jes, attribution lands as “via {label}” on the post, and any subscribed webhook fires.
What you can do
Publish content
Create Jes (text + media), JesClips (short video), and comments. Bounces and quotes too.
Read engagement
Look up the comment thread on a Jes by ID; read like/comment/bounce/save counts.
Receive events
Register HTTPS endpoints; we POST HMAC-signed payloads whenever the bound account publishes.
Stay in control
Scope keys to exactly what they need. Expiry, IP allowlist, instant revoke from settings.
What you can't do
Discovery stays in the Jestha app. There is no scope, no combination of scopes, that exposes the home feed, JeHub feeds, trending, search, or other users' profiles via API key. Apps can publish to and engage with Jestha — they can't replace it.
Next steps
- API keys — generate, authenticate, store, rotate.
- Scopes — pick the minimum permissions your integration needs.
- Rate limits — caps, quotas, media constraints, and what 429 looks like.
- Webhooks — subscribe to events and verify signatures.
- Developer Terms — what you agree to when you generate a key.