Our Multi-step API monitor type allows users to interact with their critical APIs directly. For some monitoring use-cases, data must be sent to the API, for example when executing POST requests to create a new object, or a PUT/PATCH request to update an existing object. In such cases, it is important to include a Content-Type header to inform the receiving API of the type of data that is coming in (JSON, XML, form data, etc.) so that it knows how to parse the request. An API will commonly return errors if it receives a request body without a Content-Type header.
Up until now, such headers had to be added to the Multi-step API monitor step(s) manually. As of this update, we are automatically detecting the content type, and adding the correct Content-Type header, for JSON, XML, or form data request bodies. This change will help users configure POST, PUT, and PATCH requests in their Multi-step API monitors.