SUsuperwall
Users V3

Set User Synced Attributes

Changed on

Sets attributes on the user via the events pipeline — the same path SDK user_attributes events take — so values land in both the subscriptions store and analytics. Propagation is asynchronous (typically seconds). The accepted field in the response means the request passed validation and was handed to the pipeline — it is not a read-back of the stored snapshot; use GET /v3/users/{app_user_id}/attributes to observe persisted values. Requires users:write scope.

post/v3/users/{app_user_id}/attributes

Request

  • Base URL
    https://api.superwall.com
  • URL
    https://api.superwall.com/v3/users/{app_user_id}/attributes
  • Auth
    • HTTP bearer
    • or API key in cookie accounts_superwall_token
    • or HTTP bearer

Path parameters

app_user_idstring required

App user identifier

Query parameters

application_idstring required

Request body

attributesobject required

Attribute key/value pairs to set on the user. Values must be scalars.

Response

Success

object'user_synced_attributes' required
app_user_idstring required
acceptedobject required

Changes

  • 778a11cd2c15Revision changes
    • warning

      added the new credentials_missing enum value to the / response property for the response status

    • warning

      added the new credentials_missing enum value to the / response property for the response status

    • warning

      added the new credentials_missing enum value to the / response property for the response status

    • warning

      added the new credentials_missing enum value to the / response property for the response status

    • info

      added subschema #1 subschema #2 to the response body anyOf list for the response status

    • info

      added subschema #1 subschema #2 subschema #3 subschema #4 subschema #5 to the response body anyOf list for the response status

    • info

      removed subschema #1 subschema #2 from the response body anyOf list for the response status

    • info

      removed subschema #1 subschema #2 subschema #3 subschema #4 subschema #5 from the response body anyOf list for the response status

  • 217c96dc9a29Revision changes
    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from number to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    This list may be incomplete.