Skip to main content
Version: v2

Create User

Creates a user with the specified details.

This API performs an upsert (insert or update) for a user. There is no need to check that a user exists before calling this API as it will either insert the user if it doesn't already exist or update it if it does based on the uid. A user is updated if the given uid is already associated with an identified user. Otherwise, a new user is created.

This request can be made idempotent.

Verifying that a user has been created in Fullstory

If you'd like additional confirmation that the user has been created, you can make a Get User request using the id in the Create User response. If the user was created successfully, a user will be returned and the response will include an app_url field that deep links to that user’s profile card in Fullstory. You can also query for the user with the List Users endpoint and get an app_url, provided that the user was created with a uid or email property.

The user will not be available in search/analytics reports in Fullstory until they have some activity associated with them (sessions or events).

Header Parameters
    Idempotency-Key string optional

    Optional header for making the request idempotent

Request Body required
    uid string optional

    Possible values: <= 256 characters

    The application-specific ID you've given to the user

    display_name string optional

    Possible values: <= 256 characters

    The nice-looking name for this user

    email string optional

    Possible values: <= 128 characters

    The email address associated with this user

    properties object optional

    Properties that provide additional information about your user.

    • Up to 500 unique properties are allowed.
    • Property names must be a sequence of alphanumeric characters A-Z, a-z, or 0-9 and underscores ("_").
    • Property names must start with an alphabetic character (A-Z or a-z).
    • The maximum property name length is 512 characters.
    • Property values may also contain nested objects. Properties within nested objects must still conform to the naming requirements. For nested objects, the property name including the dotted concatenation of all its parent properties must still be under the length limit of 512 characters.
    • Property values have a maximum size of 8192 bytes. If the value for the property is larger than this limit, the property will be rejected.
    schema object optional

    Optional schema declaration, to define the structure of the data and override Fullstory's default type inference.

    properties object optional

    A mapping of field names to their corresponding types.

Responses
200

A successful response.


{
"id": "987654321"
}

Additional Information

Loading...