1. Users
  2. Identify Call
POST

/v1/identify

X-Api-Key*

The identify endpoint serves three purposes:

  1. It can be used to pass user-level features after (or before) a price has already been tied to them using the main price endpoint.
  2. It can be used to link IPs to user_ids so that prices persist to a user as they see a price -> login in -> check the price again.
  3. It is used during mobile integrations to inform Corrily about original Apple and Google purchase IDs.

Body Params

user_idRequired
string
ip
string

An IP you wish to tie the user to. For more information read our anonymous users guide.

features
object

An object containing arbitrary key-value pairs that represent characteristics of this user which may affect their optimal price. The keys can be any valid JSON key. The values can be strings, integers, or floats.

apple_original_transaction_id
object

Pass an original_transaction_id for a user when they purchase an IAP product. (Note that in the backend, this will not overwrite any previously stored transaction IDs for this user).

google_purchase_token
object

Pass an purchaseToken for a user when they purchase an in-app product. (Note that in the backend, this will not overwrite any previously stored purchase tokens for this user).

Response

status
string
curl --request POST \
     --url https://client.corrily.com/v1/identify \
     --header 'Accept: application/json' \
     --header 'Content-Type: application/json' \
     --data '{ user_id: "string", features: {source: "youtube"} }'
{
  "status": "ok"
}