Skip to main content
Call POST /auth/upgrade to convert a guest session into a full registered account. You must be authenticated with the guest account’s JWT. All data created during the guest session — clothing items, outfits, and other records — is preserved under the same user ID after the upgrade. The same access token and refresh token remain valid after the call.

Endpoint

Request body

string
required
Email address for the new account. Must be unique across all registered accounts.
string
required
Username for the new account. Must be unique across all registered accounts.
string
required
Password for the new account.
string
Optional profile picture reference to associate with the account.

Response fields

Status: 201 Created
string
required
The unique identifier for the user. This is the same ID that was assigned during the guest session.
string
required
The username set during upgrade.
string
required
The email address set during upgrade.
boolean
required
Always false after a successful upgrade.
string
required
ISO 8601 timestamp of when the account was originally created (during the guest session).
string
required
ISO 8601 timestamp of when the account was last updated.
string
Profile picture reference, if one was provided in the request.

Example

cURL
Response
Call this endpoint after a user completes onboarding in your app to preserve all the data they created as a guest. There is no need to re-authenticate — your existing tokens continue to work.