List federation inbox rows

GET

/admin/federation/inbox

• Local development behind nginx (port 8088 by default)

Returns inbound activities from federation_inbox in their landed state (pending / processed / rejected / failed). Filterable by peer + status + activity type + date range; paginated. Gated on system.admin.

Read-only — inbox rows can’t be re-queued in the same way as outbox rows; the activity_uri UNIQUE constraint means a re-delivered envelope just lands on the existing row idempotently. Admins investigating rejections need to coordinate with the sender’s outbox queue instead.

Authorizations

• cookieAuth
• bearerAuth

Parameters

Query Parameters

peer_id

string format: uuid

status

string

Allowed values: pending processed rejected failed

activity_type

string

since

string format: date-time

limit

integer

default: 100 >= 1 <= 500

cursor

string

Responses

200

Inbox rows matching the filter.

object

items

required

Array<object>

One row in federation_inbox. Captures what arrived from a peer + how the inbox + dispatcher chain treated it (pending / processed / rejected / failed). Read-only via the admin UI — the activity_uri UNIQUE constraint means re-delivery is idempotent on the existing row.

object

id

required

string format: uuid

activity_uri

required

string

peer_id

required

string format: uuid

actor_uri

required

string

activity_type

required

string

object_kind

string

nullable

object_id

string format: uuid

nullable

http_sig_key

string

status

required

string

Allowed values: pending processed rejected failed

reject_reason

§12.1 reject reason when status=rejected.

string

nullable

dispatch_attempts

required

integer

last_attempt_at

string format: date-time

nullable

last_error

string

nullable

received_at

required

string format: date-time

processed_at

string format: date-time

nullable

correlation_activity_id

Local activities row the dispatcher created for this inbound envelope.

string format: uuid

nullable

next_cursor

string

nullable

400

Malformed request

object

error

required

Human-readable error summary

string

Example

the request could not be completed

401

Authentication required, missing, or invalid

object

error

required

Human-readable error summary

string

Example

the request could not be completed

Example

{
  "error": "authentication required: sign in and retry with a valid session or API token"
}

403

Authenticated but missing required capabilities

object

error

required

Human-readable error summary

string

Example

the request could not be completed