Branches are the community containers in Artemis — each branch has its own subscribers, moderators, rules, and post feed. The Branches API lets you enumerate available branches, read metadata, subscribe or unsubscribe users, create new branches, search within a branch, and compose multi-branch feeds. Routes follow theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/artemis-development-group/artemis/llms.txt
Use this file to discover all available pages before exploring further.
/r/:branch/ prefix for branch-specific actions and /branches/ for site-wide branch listings.
GET /branches/:where.json
Returns a paginated listing of branches across the site. Replace:where with one of the recognized category names.
The listing category. One of
popular, new, default, gold, or employee.Fullname cursor for forward pagination.
Fullname cursor for backward pagination.
Number of branches to return. Maximum is 100.
The branch’s URL slug (e.g.
programming).The branch’s display title.
Total subscriber count.
Short description shown in listings.
Whether the branch is marked as NSFW.
The branch’s relative URL.
GET /r/:branch/about.json
Returns full metadata for a single branch.The branch name (URL slug).
The branch’s base-36 ID.
Approximate number of users currently browsing the branch.
Full sidebar text in raw Markdown.
Text shown on the submission form, set by moderators.
Visibility setting:
public, restricted, or private.Allowed post kinds:
any, link, or self.POST /api/subscribe
Subscribes or unsubscribes the authenticated user from a branch. Requires thesubscribe OAuth2 scope.
Use
sub to subscribe or unsub to unsubscribe.The fullname of the branch (e.g.
t5_2fwo). Provide either sr or sr_name.The display name of the branch (e.g.
programming). Provide either sr or sr_name.Subscribing to a private branch requires that the authenticated user already has view access to it.
POST /branches/create
Renders the branch creation form (GET) and processes a new branch submission. In the API context this route corresponds to the newartemis action in the front controller. Authentication is required.
Pre-fills the branch name field when loading the creation form via GET.
GET /r/:branch/search.json
Searches within a specific branch’s posts.The branch name to restrict the search to.
The search query string.
Sort order for results. One of
relevance, hot, top, new, or comments.Time window when
sort is top. One of hour, day, week, month, year, or all.Number of results to return. Maximum is 100.
Fullname cursor for forward pagination.
Multi-branch feeds
Multi-branch feeds let a user combine several branches into a single listing view. The route follows the pattern/user/:username/m/:multipath.
The owner of the multi-branch feed.
The slug identifying the multi-branch feed within the user’s account.
hot, new, rising, top, and controversial.
You can manage multi-branch feeds programmatically through the /api/multi/ endpoints:
| Method | Path | Description |
|---|---|---|
GET | /api/multi/mine | List the current user’s multi-branch feeds. |
GET | /api/multi/user/:username | List multi-branch feeds owned by a specific user. |
GET/PUT/DELETE | /api/multi/*multipath | Read, create/update, or delete a multi-branch feed. |
GET/PUT/DELETE | /api/multi/*multipath/r/:srname | Read, add, or remove a branch from a feed. |
GET/PUT | /api/multi/*multipath/description | Read or update the feed’s description. |
POST | /api/multi/copy | Copy an existing multi-branch feed. |
POST | /api/multi/rename | Rename a multi-branch feed. |
Branch about pages
Several sub-pages under/r/:branch/about/ expose branch-level metadata and moderation surfaces:
| Path | Description |
|---|---|
/r/:branch/about/rules | The branch’s posted rules. |
/r/:branch/about/sidebar | The branch sidebar text. |
/r/:branch/about/sticky | The branch’s stickied post. |
/r/:branch/about/flair | Flair template listing for the branch. |
/r/:branch/about/edit | Branch settings editor (moderators only). |
/r/:branch/about/traffic | Traffic statistics (moderators only). |