Solved

400 Bad Request Error on Segmentation

  • 8 September 2022
  • 1 reply
  • 96 views
J

Hello,

 

I am trying to retrieve data using the segmentation endpoint, but I keep getting a 400 bad request error. We have an event named PUSH_NOTIFICATION/OPEN on our Amplitude, but it does not seem to work. I have also tried with the ce: prefix on the event type, but that also returns a 400 error.

 

Below is the curl request, with authorization headers removed of course.

curl --location -g --request GET 'https://amplitude.com/api/2/events/segmentation?e={"event_type":"PUSH_NOTIFICATION%2FOPEN"}&start=20220904&end=20220907&n=any'

 

 

Thanks!

icon

Best answer by Denis Holmes 9 September 2022, 11:23

View original

1 reply

Denis Holmes
Rank
Userlevel 6
Badge +8

Hi @jacksonhuether ,

 

Thanks for writing into chat! An error 400 usually means something has gone wrong with the API call itself on your end which could be incorrect syntax, for example. Can you send me the chart you are trying to reach? I can then make the call for you and send it to you in a private message. Thank you!

 

Kind Regards,
Denis

Reply


Terms & ConditionsCookie settings