List federation outbox rows
GET /admin/federation/outbox
Returns per-recipient queued / sent / failed / cancelled rows from federation_outbox. Filterable by peer + status
- activity type + date range; paginated. Gated on
system.admin.
Each row carries the activity_id back-reference so the admin UI can render the originating envelope alongside the delivery state.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Filter by the originating activity’s verb (Like / Create / aa:Share etc.).
RFC3339 timestamp; only rows created at or after this.
Pagination cursor from a prior response (opaque).
Responses
Section titled “ Responses ”Outbox rows matching the filter.
object
One row in the per-recipient federation_outbox queue . Derived from the activities ledger by the dispatcher per design §3.1; delivered by the worker per §3.3. The admin UI surfaces queued / sent / failed / cancelled rows for operator visibility into outbound federation traffic.
object
Per-recipient actor URL within the peer; null = broadcast.
Delivery attempt count (caps at 5 before terminal-fail).
Wall-clock time of the next attempt per the §3.4 backoff schedule.
Failure detail captured on the most recent attempt. For failed rows, may carry a §12.1 reject reason from the receiver — the admin UI maps these to retriable / non-retriable warnings on the re-queue confirmation prompt.
HTTP-Sig keyId used on the successful delivery (forensics).
Malformed request
object
Human-readable error summary
Example
the request could not be completedAuthentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Authenticated but missing required capabilities
object
Human-readable error summary
Example
the request could not be completed