(This is also added as a comment on https://community.amplitude.com/topic/show?tid=614&fid=57 - but since that one is marked solved, I’m not sure it’ll get any attention there.)
I’m hitting this too, and changing my payload to encase the identifications in a string didn’t help. Working in python, and using this data as a json body in a POST to https://api.amplitude.com/identify. (Also tried api2.)
I’m previously tried:
{
'api_key': '<my-key>',
'identification': i{
'user_id': 'my_id',
'user_properties': {'email': 'me@mydomain.com'}
}]
}
After reading the tid=614 thread, I tried:
{
'api_key': '<my-key>',
'identification': 'f{"user_id": "my_id", "user_properties": {"email": "me@mydomain.com"}}]'
}
I’m still getting the very uninformative “missing_event” 400 error.
Meanwhile, a direct curl call that follows the style given on https://developers.amplitude.com/docs/identify-api, with the two --data arguments (--data api_key=<my-key> and --data identification=-{...}]), works. (Returns 200, effectively changes my email.)
(Is there a difference between the two --data arguments and one JSON dictionary?)