Issue with Sending Integer Value via Multipart Entity in HTTP Connector

CloverDX Platform
1

Hi,

I’m currently working on performing a POST request to an API using the HTTP Connector component with a multipart entity.

Based on the edge and the data I need to provide to the API, I’ve configured the correct fields in the Ignored Fields section and added them to the Multipart Entities.

I then mapped the data from the edge to the corresponding Multipart Entities using the Input Mapping.

So far, everything works fine, except for one field on the API that expects an integer. From what I can see, the Multipart Entity only allows sending strings. This results in the following response from the API:

{"success":false,"error":"Validation failed: org_id: The value \u0027\u00222027\u0022\u0027 is not a valid \u0027integer\u0027.","code":"ERR_SCHEMA_VALIDATION_FAILED"}

So the issue is that I’m sending the org_id field in quotes (as a string), whereas the API expects it as a raw integer.

Is there a way to send this field as an integer instead of the default string?

2

Hi Peter,

Thank you for your post! Unfortunately, there is no straightforward way to achieve this using a multipart entity. The multipart/form-data content type does not support specifying or recognizing data types like Integers or Booleans, everything is treated as plain text in “data blocks” as binary code or in string chunks.

Based on the information provided, it sounds like you have a table where one of the columns (e.g., org_id) is an integer. If you’re trying to send this data as a structured table to an API, a better approach would be to use application/json as the content type. JSON fully supports data types such as integers, booleans, and strings, which are otherwise tricky to preserve in multipart formats. Most APIs also accept JSON-formatted payloads, so this should work in your favor.

If application/json isn’t an option for your use case, could you please share a sample of your source data and let us know which API you’re targeting? With that context, we can analyze the situation in more detail and offer a more tailored solution.

Best regards,
Tom.

3

Hi Tom,

Thanks for your reply. I changed the Content-Type to application/json and also had to change the content to JSON format, but that was indeed the solution!

Kind regards,
Peter

1 Like