Build your own native client for iOS, Android, desktop or the web with the Subreply API. Third-party apps are encouraged to adopt the "sub" or "reply" naming convention — such as Subchat, Sublevel, Subdroid or Macreply — and can extend the core experience with features like inline media previews, instant translation and custom notifications.
Authenticate by requesting a token from the /api/login endpoint and passing it in the Authorization: Bearer header on subsequent requests.
Paginate any GET endpoint by appending the ?p=number query parameter.
GET Endpoints
/api/feed— returns feed entries/api/following— returns following list/api/followers— returns followers list/api/mentions— returns received mentions/api/replies— returns received replies/api/saved— returns saved entries/api/people— optionalqparam to search people/api/discover— optionalqparam to search content/api/trending— returns trending entries/api/messages— returns last received messages/api/notifications— returns notification counts/api/reply/{id:int}— returns reply details, ancestors and kids/api/{username}/message— returns messages with member/api/{username}/posts— returns member posts/api/{username}— returns member details
POST Endpoints
/api/login— fields: username*, password* params; returns token and user/api/register— fields: username*, email*, password1*, password2*, first_name, last_name, emoji, birthday, location params; returns token and user/api/thread— fields: content* param; returns thread details/api/reply/{id:int}— fields: content* param; returns reply details/api/{username}/send— fields: content* param; returns message details
PATCH Endpoints
/api/edit/{id:int}— fields: content* param; returns reply details/api/profile— fields: username*, email*, first_name, last_name, emoji, birthday, location, link, description params; returns user details
POST Actions
/api/unsend/{id:int}/api/{username}/clear/api/delete/{id:int}/api/save/{id:int}/api/unsave/{id:int}/api/follow/{username}/api/unfollow/{username}