Solved

Getting a 'missing_event' response on identify request

  • 14 November 2021
  • 4 replies
  • 37 views

Badge

 

Hello,

I’m encountering an error where trying to run the identify request. I’m getting in the response (with no formatting) ‘missing_event’. Not in the format that is describe in your documentation.

im sending an identify request as per the documentation: https://developers.amplitude.com/docs/identify-api

to this end point: https://api.amplitude.com/identify
im sending this as my json body:

{

"api_key": AMPLITUDE_API_KEY,

"identification": [

{

"user_id": "kqlvwyvomsxnaets_170",

"user_properties": {

"userRole": "owner"

}

}

]

}

icon

Best answer by anuriel 27 November 2021, 16:28

View original

4 replies

Userlevel 2
Badge +2

Hi @anuriel - hope to help you with this! Would you mind trying this endpoint in your Identify call? 

https://api2.amplitude.com/identify

(please note it is identical to the endpoint you have already tried except there is a “2” after “api”)

Please let me know how this goes for you!

Badge

First I’d like to say thanks for the help!

it seems like I’m still getting the missing_event error.

 

I’m attaching the post request using curl that im running maybe the request will be clearer there…@jmagg any chance you can try running the request with your api key and see what you get?

 

curl --location --request POST 'https://api2.amplitude.com/identify' \

--header 'Content-Type: application/json' \

--data-raw '{

"api_key": API_KEY,

"identification": [

{

"user_id": "kqlvwyvomsxnaets_170",

"user_properties": {

"company": "kqlvwyvomsxnaets",

"industry": "healthcare",

"numberOfEmployeeRange": "21-50",

"signupTimestamp": "1616678036",

"conversionToPaidTimestamp": "1628003369",

"planId": "enterprise",

"userRole": "owner"

},

"country": "Israel"

}

]

}'

Badge

so after talking to one of their sales people that send the question to one of the tech people, I got this information:

“missing_event” gets sent when they are not able to parse the request correctly.

looks like a general error that isn't explained…

the way I got it to work in the end is sending identification as a json stringify instead of the whole json object. which is kinda weird but what ever

so my payload was:

{

"api_key": API_KEY,

"identification": “[{“user_id”:”blablabla”...}]”

}

Userlevel 2
Badge +2

Hi @anuriel - sorry for the delayed response here! Glad to hear you resolved the issue :slight_smile:

Reply