Calling an OData action via Postman fails with `ODP_DESERIALIZATION_ERROR`, even though the exact same operation succeeds when triggered through Aurena itself — what's different about the raw request Postman is sending?

Q: Calling an OData action via Postman fails with `ODP_DESERIALIZATION_ERROR`, even though the exact same operation succeeds when triggered through Aurena itself — what's different about the raw request Postman is sending?

Add these two headers to the Postman request: Accept: application/json;odata.metadata=full;IEEE754Compatible=true and Content-Type: application/json;IEEE754Compatible=true. Aurena's own OData client sends these specific header values by default, and a plain Postman request without them can fail deserialization on the server side — adding both headers to match what Aurena actually sends resolves the error.

Answer

Add these two headers to the Postman request: Accept: application/json;odata.metadata=full;IEEE754Compatible=true and Content-Type: application/json;IEEE754Compatible=true. Aurena's own OData client sends these specific header values by default, and a plain Postman request without them can fail deserialization on the server side — adding both headers to match what Aurena actually sends resolves the error.

← Browse Integrations and APIs questions