Fake follows API

5,000 follows from the Social API, a fake social media API. follower_id follows followee_id.

Reads with filters, sorting, search and relations; writes that answer like a real server and stay in your session token. Same ids on every build. Free, no key, CORS open.

Connect

List: https://api.sondahub.com/v1/social/follows
One record: https://api.sondahub.com/v1/social/follows/{id}
OpenAPI 3: https://api.sondahub.com/v1/social/openapi.json
GraphQL: https://api.sondahub.com/v1/social/graphql
JSON file: https://api.sondahub.com/data/social/follows.json
MCP: https://api.sondahub.com/mcp · list_records

The first three follows

curl "https://api.sondahub.com/v1/social/follows?limit=3"

Sample records

Records 1 to 3 of 5,000, exactly as GET /v1/social/follows/{id} answers them. The data file holds all of them.

[
  {
    "id": 1,
    "created_at": "2024-03-18T12:02:04Z",
    "updated_at": "2024-03-18T12:02:04Z",
    "follower_id": 648,
    "followee_id": 684,
    "status": "active",
    "notifications": false
  },
  {
    "id": 2,
    "created_at": "2025-09-29T10:34:24Z",
    "updated_at": "2025-09-29T10:34:24Z",
    "follower_id": 257,
    "followee_id": 667,
    "status": "active",
    "notifications": false
  },
  {
    "id": 3,
    "created_at": "2024-10-12T04:32:21Z",
    "updated_at": "2024-10-12T04:32:21Z",
    "follower_id": 313,
    "followee_id": 418,
    "status": "active",
    "notifications": false
  }
]

Fields

Field	Type	Notes
`id`read-only	int	Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed.
`created_at`read-only	datetime	When the record was created (ISO 8601, UTC).
`updated_at`read-only	datetime	When the record last changed.
`follower_id`required	int → users
`followee_id`required	int → users
`status`	enum	`active` `pending` `blocked`
`notifications`	bool

Relations: follower → one user through follower_id; followee → one user through followee_id. Use ?expand=follower,followee to embed them, or the nested routes.

Endpoints

POST refuses following yourself and duplicates (409); following a private user starts pending; active follows move both users’ counters.

GET/v1/social/followsA page, with every filter, sort, search, field and expand option.

POST/v1/social/followsCreate one: 201 with the record, its id, a Location header and the session token that keeps it; 422 names each field that is wrong.

GET/v1/social/follows/{id}One record, with an ETag; If-None-Match earns a 304.

PATCH/v1/social/follows/{id}Change the fields you send.

PUT/v1/social/follows/{id}Replace the record; required fields must all be there.

DELETE/v1/social/follows/{id}Answers 200 with what was removed (a real server’s 204 lives at /v1/utils/status/204); gone for the session.

GET/v1/social/follows/{id}/followerThe user this record points at.

GET/v1/social/follows/{id}/followeeThe user this record points at.

Try it

List with a filter

curl "https://api.sondahub.com/v1/social/follows?status=pending&expand=follower&limit=3"

One record

curl https://api.sondahub.com/v1/social/follows/1?expand=follower

Create

curl -i -X POST https://api.sondahub.com/v1/social/follows \
  -H "Content-Type: application/json" \
  -d '{"follower_id":1,"followee_id":2,"status":"active"}'

Read it back: newest first (send the session token)

curl "https://api.sondahub.com/v1/social/follows?sort=-id&limit=3" \
  -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"

Change one field

curl -X PATCH https://api.sondahub.com/v1/social/follows/1 \
  -H "Content-Type: application/json" \
  -d '{"status":"pending"}'

Delete the one you created

curl -X DELETE https://api.sondahub.com/v1/social/follows/5001 \
  -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"

Query recipes

Every list option works on follows; these are ready to paste. All the options.

What	Request
Page 2, 50 at a time (of 5,000)	/v1/social/follows?page=2&limit=50
Only status = active	/v1/social/follows?status=active
Newest first by created at	/v1/social/follows?sort=-created_at&limit=5
Only some fields	/v1/social/follows?fields=id,follower_id&limit=5
Embed the follower	/v1/social/follows/1?expand=follower
Just the count	/v1/social/follows?limit=1&fields=id

GraphQL

The same follows as the follows query on https://api.sondahub.com/v1/social/graphql, and one follow as follow(id: 1). Introspection is on. More on the GraphQL API.

{
  follows(limit: 3, sort: "-id", filter: { status: active }) {
    total
    data {
      id follower_id followee_id status
      follower { username }
    }
  }
}

Run it

curl https://api.sondahub.com/v1/social/graphql -H "Content-Type: application/json" -d '{"query": "{ follows(limit: 3, sort: \"-id\", filter: { status: active }) { total data { id follower_id followee_id status follower { username } } } }"}'

From an AI agent (MCP)

The MCP server reaches the same rows with list_records, get_record, create_record, update_record and delete_record, and as the resource sondahub://social/follows.

tools/call

curl https://api.sondahub.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_records","arguments":{"api":"social","collection":"follows","filters":{"status":"active"},"limit":3}}}'

More in the Social API

users (800) · posts (4,000) · comments (8,000) · likes (8,000)

The live streams, and the whole API on one page: Social API. Other worlds: fake e-commerce API, fake IoT API, fake banking API, fake helpdesk API, fake flight booking API, fake user directory API.