Fake social users API

800 users from the Social API, a fake social media API. Members.

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/users
One record: https://api.sondahub.com/v1/social/users/{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/users.json
MCP: https://api.sondahub.com/mcp · list_records

The first three users

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

Sample records

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

[
  {
    "id": 1,
    "created_at": "2026-03-18T09:49:24Z",
    "updated_at": "2026-03-18T09:49:24Z",
    "username": "bram_bianchi",
    "display_name": "Bram Bianchi",
    "email": "[email protected]",
    "bio": null,
    "avatar_url": "/v1/social/users/1/avatar.svg",
    "location": "Dubai, AE",
    "website": null,
    "verified": false,
    "private": false,
    "followers_count": 5,
    "following_count": 7,
    "posts_count": 7,
    "joined_at": "2026-03-18T09:49:24Z"
  },
  {
    "id": 2,
    "created_at": "2022-01-22T22:15:23Z",
    "updated_at": "2022-01-22T22:15:23Z",
    "username": "bram_moore",
    "display_name": "Bram Moore",
    "email": "[email protected]",
    "bio": "Quiet streets after the rain. Here for the dogs.",
    "avatar_url": "/v1/social/users/2/avatar.svg",
    "location": "Rio de Janeiro, BR",
    "website": "https://bram_moore.example.com",
    "verified": false,
    "private": false,
    "followers_count": 8,
    "following_count": 5,
    "posts_count": 14,
    "joined_at": "2022-01-22T22:15:23Z"
  },
  {
    "id": 3,
    "created_at": "2026-03-08T03:17:38Z",
    "updated_at": "2026-03-08T03:17:38Z",
    "username": "mia_lopez",
    "display_name": "Mia Lopez",
    "email": "[email protected]",
    "bio": null,
    "avatar_url": "/v1/social/users/3/avatar.svg",
    "location": null,
    "website": null,
    "verified": false,
    "private": true,
    "followers_count": 2,
    "following_count": 6,
    "posts_count": 3,
    "joined_at": "2026-03-08T03:17:38Z"
  }
]

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.
`username`required	string	Unique handle.
`display_name`required	string
`email`	string
`bio`	text
`avatar_url`	string	A generated SVG served by the hub.
`location`	string
`website`	string
`verified`	bool
`private`	bool
`followers_count`read-only	int
`following_count`read-only	int
`posts_count`read-only	int
`joined_at`	datetime

Relations: posts → the posts whose author_id is this user; comments → the comments whose author_id is this user; likes → the likes whose user_id is this user; followers → the follows whose followee_id is this user; following → the follows whose follower_id is this user. Use ?expand=posts,comments,likes,followers,following to embed them, or the nested routes.

Endpoints

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

POST/v1/social/usersCreate 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/users/{id}One record, with an ETag; If-None-Match earns a 304.

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

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

DELETE/v1/social/users/{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/users/{id}/postsIts posts, as a page with all the list options.

GET/v1/social/users/{id}/commentsIts comments, as a page with all the list options.

GET/v1/social/users/{id}/likesIts likes, as a page with all the list options.

GET/v1/social/users/{id}/followersIts follows, as a page with all the list options.

GET/v1/social/users/{id}/followingIts follows, as a page with all the list options.

Try it

List with a filter

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

One record

curl https://api.sondahub.com/v1/social/users/1

Its posts

curl "https://api.sondahub.com/v1/social/users/1/posts?limit=5"

Create

curl -i -X POST https://api.sondahub.com/v1/social/users \
  -H "Content-Type: application/json" \
  -d '{"username":"camila_fernandez","display_name":"A display name"}'

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

curl "https://api.sondahub.com/v1/social/users?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/users/1 \
  -H "Content-Type: application/json" \
  -d '{"username":"Changed username"}'

Delete the one you created

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

Query recipes

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

What	Request
Page 2, 50 at a time (of 800)	/v1/social/users?page=2&limit=50
Newest first by created at	/v1/social/users?sort=-created_at&limit=5
Username contains “bram”	/v1/social/users?username_like=bram
Full-text search	/v1/social/users?q=bram
Only some fields	/v1/social/users?fields=id,username&limit=5
Its posts (nested route)	/v1/social/users/1/posts?limit=5
Just the count	/v1/social/users?limit=1&fields=id

GraphQL

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

{
  users(limit: 3, sort: "-id") {
    total
    data {
      id username display_name email
      posts(limit: 2) { id }
    }
  }
}

Run it

curl https://api.sondahub.com/v1/social/graphql -H "Content-Type: application/json" -d '{"query": "{ users(limit: 3, sort: \"-id\") { total data { id username display_name email posts(limit: 2) { id } } } }"}'

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/users.

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":"users","limit":3}}}'

More in the Social API

posts (4,000) · comments (8,000) · likes (8,000) · follows (5,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.