Get a member
One member with their connected accounts embedded as identities.
email and billing_email are present only when the calling token carries project-user:view, which this route requires; a roster-only token (project-user:view-any) never sees them on the list, where the keys are absent, not null. The two are not interchangeable:
| Field | Where it comes from | Safe to contact? |
|---|---|---|
| The member chose it themselves and verified it. It is their portal sign-in credential. | Yes | |
| billing_email | Whatever address they gave a payment provider at checkout. Never verified, never used for authentication. | Treat as identification only |
Members join through a bot and are never asked for an email, so for most of them email is null and billing_email is the only address on record, which is what makes it useful for matching a refund request to a subscription.
billing_email is populated automatically from the payment provider on every new payment (Stripe, PayPal, Paystack, Razorpay and Skrill). Members who last paid before that capture existed may have null until their next payment, and members who joined by redeeming an access code never had a payment at all, so they have no billing address to record.
Request
- Base URL: https://api.subscriby.net
- URL: https://api.subscriby.net/v1/projects/{project}/members/{member}
- Auth: HTTP bearer
Path parameters
The project, resolved by the route binder.
The member, resolved within the project by the route binder.
Response
The member.
Example response
{
"data": {
"id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",
"project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
"username": "@janedoe",
"first_name": "Jane",
"last_name": "Doe",
"billing_email": "jane@example.com",
"identities": [
{
"id": "6a1f0c3e-2d4b-4e8a-9c7d-1b5e3f9a2c4d",
"connector": "telegram",
"source": "handshake",
"preferred": true,
"external_id": "123456789",
"display_name": "Jane Doe",
"username": "janedoe",
"linked_at": "2026-05-18T10:05:00Z"
}
],
"status": "customer",
"joined_at": "2026-05-18T10:05:00Z",
"created_at": "2026-05-18T10:05:00Z",
"updated_at": "2026-05-18T10:05:00Z"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.