How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Pixelfed Statuses API

Creating, reading, and interacting with statuses (posts)

Pixelfed Statuses API is one of 17 APIs that Pixelfed publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Status. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a GitHub repository, authentication docs, and rate-limit docs.

This API exposes 12 operations across 11 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.1.

Requests are made against a single base URL, https://{instance}/api.

12 operations 11 paths 10 schemas 1 DELETE4 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1
Base URL
https://{instance}/api
Authentication
OAuth 2.0, HTTP Bearer
Contact
License
Resource Areas
1

Authentication & Security 2

Pixelfed Statuses API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 4 scopes. It accepts HTTP bearer tokens (OAuth2) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 12

Across 11 paths, the API surfaces 12 operations — 1 DELETE, 4 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Statuses 12

Creating, reading, and interacting with statuses (posts)

POST
/v1/statuses
Post a new status
createStatus body → 200401422
GET
/v1/statuses/{id}
Get a single status
getStatus 1 param → 200404
DELETE
/v1/statuses/{id}
Delete a status
deleteStatus 1 param → 200401404
GET
/v1/statuses/{id}/context
Get status context (thread)
getStatusContext 1 param → 200404
GET
/v1/statuses/{id}/favourited_by
Get accounts that favourited the status
getStatusFavouritedBy 2 params → 200404
GET
/v1/statuses/{id}/reblogged_by
Get accounts that reblogged the status
getStatusRebloggedBy 2 params → 200404
POST
/v1/statuses/{id}/favourite
Favourite a status
favouriteStatus 1 param → 200401
POST
/v1/statuses/{id}/unfavourite
Undo favourite on a status
unfavouriteStatus 1 param → 200401
POST
/v1/statuses/{id}/reblog
Reblog a status
reblogStatus 1 param body → 200401
POST
/v1/statuses/{id}/unreblog
Undo reblog of a status
unreblogStatus 1 param → 200401
POST
/v1/statuses/{id}/bookmark
Bookmark a status
bookmarkStatus 1 param → 200401
POST
/v1/statuses/{id}/unbookmark
Remove bookmark from a status
unbookmarkStatus 1 param → 200401

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Status (28 properties), Account (17 properties), MediaAttachment (8 properties), Poll (7 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
Mention
object
4 properties
Poll
object
7 properties
Tag
object
3 properties
Emoji
object
4 properties
Field
object
3 properties
MediaAttachment
object
8 properties
PreviewCard
object
5 properties
Status
object
Represents a status (post) in the Pixelfed / Mastodon API
28 properties
Account
object
Represents a Pixelfed / Mastodon-compatible account
17 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pixelfed-statuses-api-openapi.yml Raw ↑

Other APIs Pixelfed publishes across the network.

Pixelfed Accounts API
Pixelfed Blocks and Mutes API
Pixelfed Bookmarks API
Pixelfed Collections API
Pixelfed Direct Messages API
Pixelfed Discovery API
Pixelfed Favourites API
Pixelfed Follow Requests API
Pixelfed Instance API
Pixelfed Lists API
Pixelfed Media API
Pixelfed Notifications API
Where this information came from

This is an independent, third-party profile of Pixelfed Statuses API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.