Skip to main content
Sets and deletes properties on the profile of one identified user. Keys that you do not send keep their values. The response returns the merged properties, so you do not need a second read.

Authentication

Use an API key (ua_api_..., or an older ua_mcp_... key) with the profiles:write scope. See Authentication.
  • The key works on its own project only. A key of another project gets 404.
  • The key acts for the member who created it. That member must be an owner, admin or editor.
  • Call this endpoint from a server. A request with a browser Origin header gets 403.
Editors can also change properties in the dashboard on the profile’s Properties tab.

Path parameters

A profile is keyed by user_id. An anonymous visitor has no profile to write to: identify the visitor first. If no profile exists for the user_id, the write creates it.

Body

A flat object of properties. Send 1 to 50 keys. Known properties such as discord_id and steam_id must be strings and pass a light format check. Any other key is a custom property.

Response

200:
The write goes through the event pipeline. Reports, the Users page and GET reads show it after a few seconds.

Delete a property

Send null. Set and delete can go in the same request:
A deleted property is gone from the profile, the Properties tab and MCP get_profile until you set a new value. Deleting email also deletes the derived company_domain. A Discord bot or your website links a player to a Discord account with one call. The bot knows the Discord user ID (a snowflake), and your game or site knows the user_id:
To unlink, send { "discord_id": null, "discord": null }. Keep the key in the bot’s server-side secrets, never in a client.

Errors

PUT is idempotent: you can retry the same body after a 429 or a 5xx.