Skip to main content
POST
Create a user

Authorizations

X-PARTNER-API-KEY
string
header
required

Your FanFeed partner API key, issued to your organization.

FanFeed trusts your authentication: the key identifies you, and the user_id in the path identifies which of your users the request is for. FanFeed performs no end-user authentication of its own.

Treat the key as a server-side secret. See the guide for what that implies for the camera-roll ingest path, which is the one call that naturally originates on-device.

Body

application/json
email
string<email>
required

The only required field.

Example:

"fan@example.com"

partner_user_id
string | null

Your own identifier for this user, stored with the partner-user link so both sides can correlate. Recommended.

Example:

"partner_user_12345"

first_name
string | null

User's first name.

Example:

"Jane"

last_name
string | null

User's last name.

Example:

"Doe"

phone_number
string | null

Stored when it is not already in use by another profile, and silently ignored when it is. Never causes this call to fail.

Example:

"+12125551234"

address
object | null

Optional. Stored with the partner-user link. Not used for matching; matching is driven entirely by photo coordinates.

Response

User created or returned.

user_id
string<uuid>
required

Store this. Every other endpoint needs it.

Example:

"8f14e45f-ceea-467a-9a1e-2b4d9c3f0a11"

existing
boolean
required

true when this call reused a previously created user record instead of creating a new one.

Example:

false

created_at
string<date-time>
required
Example:

"2026-08-25T18:31:07Z"