vendor/amplitude-identify · vendor documented
Amplitude identify needs api_key and identification
Not HTTP V2. Identify updates user properties. api_key is the project key. identification is a JSON object or array. Each object needs user_id or device_id. Group identify is vendor/amplitude-group-identify.
identification is required
Amplitude returns missing_event when identification is missing or empty. The 414 is GET with a URL that is too long. Use POST form in that case; pixellint still reads the same names on the query.
What this pack matches
Rules
Codes are stable. A finding in CI, MCP, or the playground lands on the same id.
| Field | Required | What it checks | Rule ids | Source |
|---|---|---|---|---|
api_key |
required | It is the project API key. Amplitude documents it as required on GET query and POST form. Fix: Send `api_key` with the Amplitude project API key. | vendor.amplitude-identify.param.api_key.missingvendor.amplitude-identify.param.api_key.empty |
docs |
identification |
required | It is a JSON identification object or array. Amplitude documents it as required. Each object needs user_id or device_id. Fix: Send `identification` as JSON with `user_id` or `device_id`. | vendor.amplitude-identify.param.identification.missingvendor.amplitude-identify.param.identification.empty |
docs |
Validate a payload
pixellint validate url "$ARTIFACT" --rulepack vendor/amplitude-identify
Try this failing payload in the playground. Amplitude identify missing api_key.
https://api2.amplitude.com/identify?identification=%5B%7B%22user_id%22%3A%22user-13793%22%7D%5D
cargo install pixellint
·
npm install pixellint