ActivityPub Overview

ActivityPub is a W3C Recommendation that defines a protocol for decentralized social networking. It provides both a client-to-server (C2S) API and a server-to-server (S2S) federation protocol.

Specification

• Status: W3C Recommendation (January 2018), under active maintenance by the rechartered Social Web Working Group — a backwards-compatible update incorporating accepted errata is expected in late 2026
• URL: https://www.w3.org/TR/activitypub/
• Editor's Draft: w3c.github.io/activitypub — incorporates accepted errata ahead of the updated Recommendation
• Editors: Christopher Lemmer Webber, Jessica Tallon, Erin Shepherd

Two Protocols in One

ActivityPub defines two complementary protocols:

Client-to-Server (C2S)

The C2S protocol defines how clients (apps) interact with servers:

• POST to Outbox: Submit activities the user wants to perform
• GET from Inbox: Read activities sent to the user
• GET from Collections: Read followers, following, likes

note

Most Fediverse software implements a custom REST API instead of C2S. The S2S protocol is universally implemented.

Server-to-Server (S2S)

The S2S protocol defines how servers federate:

• POST to Inbox: Deliver activities to remote users
• GET Actor: Fetch remote user profiles
• GET Objects: Fetch remote content

Core Components

1. Actors

Every user or entity is represented as an Actor with:

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Person",
  "id": "https://example.com/users/alice",
  "inbox": "https://example.com/users/alice/inbox",
  "outbox": "https://example.com/users/alice/outbox",
  "preferredUsername": "alice"
}

Learn more about Actors →

2. Activities

Actions are represented as Activity objects:

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://example.com/users/alice",
  "object": {
    "type": "Note",
    "content": "Hello, world!"
  }
}

Learn more about Activities →

3. Objects

Content is represented as Objects:

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "id": "https://example.com/notes/1",
  "content": "Hello, world!",
  "attributedTo": "https://example.com/users/alice"
}

Learn more about Objects →

4. Collections

Lists of items are represented as Collections:

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "OrderedCollection",
  "id": "https://example.com/users/alice/outbox",
  "totalItems": 42,
  "first": "https://example.com/users/alice/outbox?page=1"
}

Learn more about Collections →

Required Endpoints

For All Actors

Endpoint	Method	Description
Actor URL	GET	Returns the actor's profile
Inbox	POST	Receives activities from other servers
Outbox	GET	Returns activities by this actor

For C2S (Optional)

Endpoint	Method	Description
Outbox	POST	Client submits new activities
Inbox	GET	Client reads incoming activities

Content Negotiation

ActivityPub uses content negotiation. Clients should:

Request:

GET /users/alice HTTP/1.1
Accept: application/activity+json

Response:

HTTP/1.1 200 OK
Content-Type: application/activity+json

{ ... actor JSON ... }

Accepted media types:

• application/activity+json
• application/ld+json; profile="https://www.w3.org/ns/activitystreams"

Addressing

Activities specify recipients using:

Property	Purpose
to	Primary recipients (visible)
cc	Secondary recipients (visible)
bto	Private primary recipients
bcc	Private secondary recipients
audience	Additional context

Special addresses:

• https://www.w3.org/ns/activitystreams#Public - Public visibility

Security

ActivityPub relies on:

1. HTTPS - All URLs must use HTTPS
2. HTTP Signatures - Verify request authenticity
3. Linked Data Signatures - (Optional) Sign objects themselves

Learn more about Security →

Relationship to Other Specs

Common Extensions

The Fediverse has developed de facto extensions:

Extension	Purpose	Used By
sensitive	Content warnings	Mastodon
Emoji	Custom emoji	Mastodon, Misskey
PropertyValue	Profile fields	Mastodon
IdentityProof	Identity verification	Keyoxide
Hashtag	Hashtag type	Most platforms

Implementation Status

Platform	C2S	S2S
Mastodon	❌	✅
Pleroma	✅	✅
Pixelfed	❌	✅
Lemmy	❌	✅
PeerTube	❌	✅

Next Steps

• Actors - Deep dive into Actor objects
• Activities - Activity types and handling
• Server-to-Server - Federation mechanics
• Building an Actor - Practical implementation