get_subscriber

One project member by UUID, in the list_subscribers row shape. Returns two email addresses verbatim — scrub before forwarding.

Purpose

Fetch one member (subscriber) of a project by id when you already know it — from a webhook payload's subscriber_id, a support conversation, or an earlier list. The row is the one list_subscribers returns, so a member read here is identical to the same member read from the list.

PII

Both email (member-chosen and verified) and billing_email (whatever they gave a payment provider) come back verbatim, as do the platform ids of the member's connected accounts under identities. Scrub them before forwarding to any third-party LLM, log sink or analytics surface.

Required ability

project-user:view

Input schema

{
  "type": "object",
  "required": ["member_id"],
  "properties": {
    "member_id": {
      "type": "string",
      "description": "UUID of the project member to fetch."
    }
  }
}

Output shape

{
  "data": {
    "id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",
    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
    "name": "Ada Lovelace",
    "email": "[email protected]",
    "email_verified": true,
    "billing_email": "[email protected]",
    "identities": [
      {
        "connector": "telegram",
        "external_id": "123456789",
        "display_name": "Ada Lovelace",
        "username": "ada",
        "preferred": true
      }
    ],
    "status": "customer",
    "joined_at": "2026-05-18T10:05:00+00:00"
  }
}

name is the display name Subscriby derived for the member; status is their standing in the project (lead, customer, and the churned and moderation states), not a subscription status.

identities lists the member's connected accounts, the one they prefer to be reached on first: the connector key, the platform's own id for the account, and the display name and username the platform reported. A member who only ever used the portal and connected nothing has an empty list.

Example prompts

"Who is member 2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80? The webhook only gave me the id."

"Is the member behind this support conversation a paying customer or a lead?"

"Has that member verified their email?"

Failure modes

  • RESOURCE_NOT_FOUND — unknown member_id, or a member of a project outside the token's scope.
  • AUTHENTICATION_REQUIRED — no authenticated user on the request.
  • TOKEN_MISSING_ABILITY — token lacks project-user:view.

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request