Symptom
When doing Odata API Upsert via JSON payload format, you encounter Odata API Errors response describe in below exception message samples.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Sample Error 1 (2 error message type in this category)
- <code>BadRequestException</code>
<messagelang="en-US">The post data are in the bad JSON format: Unexpected end-of-input: (1) expected close marker for Object (start marker at or (2) within/between Object entries [Source: (String) >Request Payload Body with BAD FORMAT Is shown in here in the message Exception/API Response<)</message>
Sample Error 2
- <code>BadRequestException</code>
<messagelang="en-US">The post data are in the bad JSON format: Unexpected character (''' (code 39)): expected a valid value (number, String, array, object, 'true', 'false' or 'null’) at [Source: (String) >Request Payload with BAD FORMAT Is shown in here in the message Exception/API Response<)</message>
Read more...
Environment
Successfactors HCM Suite
Product
Keywords
HTTP Response = 400, The post data are in the bad JSON format: Unexpected end-of-input, The post data are in the bad JSON format: Unexpected character, BadRequestException, Odata API Upsert Error, SuccessFactors HCM suite , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.