Skip to content
Scrappa Get API key
Lemmy API 1 credit/request

Lemmy User Profile API Documentation

GET https://scrappa.co/api/lemmy/user

Lemmy User Profile API returns the public profile of a Lemmy user as JSON: id, name, display name, bio, avatar, banner, actor id, post count, comment count, admin flag and publish date. The response also includes the user's recent posts and comments. A valid profile with zero posts is still a successful response.

Lemmy User Profile API Documentation 1 credit/request

Endpoint

Request preview
GET
https://scrappa.co/api/lemmy/user
Auth header
x-api-key
Cost
1 credit/request
username = example
Response preview
200 OK
{
    "data": {
        "user": {
            "id": 3100864,
            "bio": "A Lemmy user.",
            "name": "EatingPies",
            "avatar": "https://lemmy.world/pictrs/image/jkl012.jpeg",
            "actor_id": "https://lemmy.world/u/EatingPies",
            "is_admin": false,
            "published": "2024-01-15T10:00:00.000000Z",
            "post_count": 22,
            "display_name": "EatingPies",
            "comment_count": 2
        },
...

Parameters

Start with the required fields, then add optional filters only when your use case needs them.

Runnable path

1 required parameter needed before sending a request.

4 optional filters available.

username string Required

Lemmy username. Example: EatingPies.

Example value example
sort string Optional

Sort order for posts and comments. One of: New, Active, Hot, TopDay, TopWeek, TopMonth. Defaults to New.

Example value relevance
limit integer Optional

Items per page. Server caps at 50. Defaults to 20.

Example value 10
page integer Optional

1-based page number. Defaults to 1.

Example value 1
instance string Optional

Lemmy instance hostname. Defaults to lemmy.world. The hostname must resolve to a public address; private, loopback and unresolvable hosts are rejected without charge.

Example value example

Response Schema

Example response fields are illustrative; inspect the JSON before integrating.

Example response fields

Scan these fields before integrating.

data meta success
JSON Response
200 OK
{
    "data": {
        "user": {
            "id": 3100864,
            "bio": "A Lemmy user.",
            "name": "EatingPies",
            "avatar": "https://lemmy.world/pictrs/image/jkl012.jpeg",
            "actor_id": "https://lemmy.world/u/EatingPies",
            "is_admin": false,
            "published": "2024-01-15T10:00:00.000000Z",
            "post_count": 22,
            "display_name": "EatingPies",
            "comment_count": 2
        },
        "posts": [
            {
                "id": 53070436,
                "score": 42,
                "title": "A technology post title",
                "community": {
                    "id": 2478,
                    "name": "technology",
                    "title": "Technology"
                },
                "published": "2026-10-10T14:30:00.000000Z",
                "comments_count": 167
            }
        ],
        "comments": [
            {
                "id": 26295573,
                "score": 12,
                "content": "Comment content",
                "post_id": 53031195,
                "published": "2026-10-10T15:00:00.000000Z",
                "content_plain": "Comment content"
            }
        ],
        "has_more": true
    },
    "meta": {
        "billable": true,
        "endpoint_family": "user_profile"
    },
    "success": true
}

Errors

Handle these documented responses before retrying or showing customer-facing failures.

422

Validation Error

The username parameter is missing or invalid. This response is not billable.

{
    "errors": {
        "username": [
            "The username field is required."
        ]
    },
    "message": "The request validation failed"
}
404

User Not Found

The requested Lemmy user was not found. This response is not billable.

{
    "error": {
        "code": "NOT_FOUND",
        "message": "The requested Lemmy resource was not found."
    },
    "success": false
}
503

Upstream Unavailable

The Lemmy API is temporarily unavailable. This response is not billable.

{
    "error": {
        "code": "UPSTREAM_UNAVAILABLE",
        "message": "The Lemmy API is temporarily unavailable. Please retry."
    },
    "success": false
}

Generate Code with AI

Copy a ready-made prompt with all the endpoint details, parameters, and example responses. Paste it into ChatGPT, Claude, or any AI assistant to instantly generate working code.

Try It Live

Test this endpoint in our interactive playground with real data.