vendor/amplitude-group-identify · vendor documented
Amplitude group identify needs api_key and a group
Not /identify. Group identify writes account or company properties. identification is JSON with group_type and group_value. HTTP V2 stays vendor/amplitude.
api_key is required
Amplitude documents api_key on GET query and POST form. A path-only /groupidentify is not an identify call.
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-group-identify.param.api_key.missingvendor.amplitude-group-identify.param.api_key.empty |
docs |
identification |
required | It is a JSON identification object or array. Amplitude documents it as required. Each object carries group_type and group_value. Fix: Send `identification` as JSON with `group_type` and `group_value`. | vendor.amplitude-group-identify.param.identification.missingvendor.amplitude-group-identify.param.identification.empty |
docs |
Validate a payload
pixellint validate url "$ARTIFACT" --rulepack vendor/amplitude-group-identify
Try this failing payload in the playground. Amplitude group identify missing api_key.
https://api2.amplitude.com/groupidentify?identification=%7B%22group_type%22%3A%22Company%22%2C%22group_value%22%3A%22acme%22%7D
cargo install pixellint
·
npm install pixellint