API POST api_token accepted and rejected

Not sure if this is a bug so checking here.

I’m sending a POST to an endpoint.
If I include {‘api_token’: 1234567890} in the json body Bubble sends back 400 unrecognized field api_token.
But, if I don’t include the api_token in the json body Bubble sends back 401 permission denied.

That seems like improper behavior. If Bubble recognized the api_token field and used it for authentication, then that field shouldn’t cause a problem when the dictionary gets passed to the next step.

This topic was automatically closed after 14 days. New replies are no longer allowed.