Twittner API
Build on top of the Twittner platform. Our API gives you access to user accounts, posts, messaging, notifications, and more — everything you need to create rich integrations.
Base URL
https://twittner.com/mobile_api/
All endpoints are relative to this base URL.
Authentication
session_id
Pass the user's session token as a GET parameter on every authenticated request.
API Key
api_key
A unique key for your application instance. Required on every request.
Response Format
JSON
All responses return JSON with
code, message, and data fields.Authentication
Most endpoints require user authorization. After logging in via the
Login endpoint, you receive an auth_token
that acts as the session. Include it on every subsequent request:
https://twittner.com/mobile_api/feeds?session_id=YOUR_AUTH_TOKEN&api_key=YOUR_API_KEY
Response Structure
Every API response follows a consistent structure. Successful responses return code 200,
while errors return codes like 402 or 403.
Success response
{
"code": 200,
"message": "Success",
"data": {
...
}
}
Error response
{
"code": 402,
"message": "Error description",
"data": []
}
Quick Reference
| Concept | Details | Notes |
|---|---|---|
| API URL | [SITE]/mobile_api/[endpoint] | e.g. https://twittner.com/mobile_api/login |
| session_id | Auth token (GET parameter) | Required for authenticated actions — following, posting, messaging, etc. |
| api_key | Instance API key (GET parameter) | Unique to your Twittner instance. Find it in the admin panel under API settings. |
| Response | JSON object | Contains code, message, data |
Need help? Reach out at support@twittner.com