Users
End-users of your product who interact with feedback, comments, and votes — distinct from your team's admin users.
A user in this API represents an end-user of your product — the people who file feedback, vote on posts, and leave comments. These are stored in ProductBridge's organization_user table, which is per-org and independent of the underlying SaaS account.
The API lets you retrieve and soft-delete users. Creating users is not exposed via the public API in v1 — users are created via your portal (when they sign in to vote/comment), via integrations (Zendesk, Freshdesk, etc.), or via the AI ingestion pipeline.
Three user concepts to keep straight. ProductBridge has end-users (this resource), admin users (your team), and external users (imported from integrations). The public API only exposes end-users.
The user object
The org-scoped membership row's UUID. Stable for the lifetime of the user's link to your org.
The underlying user's UUID — same value across organizations, if the user appears in multiple orgs.
The user's email address. May be null for users who haven't supplied one.
The user's display name. May be null.
URL of the user's avatar image. May be null.
Role within the organization's portal. Defaults to "end_user".
Optional company affiliation captured from the customer record. May be null.
Optional CRM-style status (e.g. "trial", "paying", "churned"). May be null.
ISO 8601 timestamp at which the user was first linked to your organization.
Example user object
{
"id": "ff3c3ef8-b8cd-cd15-01ba-orguser000001",
"user_id": "bb3c3ef8-b8cd-cd15-01ba-useruser0001",
"email": "sally@acme.example.com",
"name": "Sally Doe",
"avatar_url": "https://acme.example.com/avatars/sally.png",
"portal_role": "end_user",
"company_name": "Acme Inc",
"customer_status": "paying",
"created_at": "2026-04-01T08:00:00.000Z"
}
What you can do
Last updated 1 week ago
Built with Documentation.AI