Batch Ingestion Error INGEST-1211-400: Why does formatted JSON fail but JSONL succeeds?

Hello ​@OmarGo2 ,

The behavior you are seeing is expected due to how Adobe Experience Platform (AEP) batch ingestion processes data.

• Issue: When uploading standard JSON via the UI, AEP expects newline-delimited JSON (JSONL) for batch ingestion. A JSON array or single JSON object cannot be parsed as multiple records in a batch. This causes the INGEST-1211-400 error with code 150: “Parsing errors occurred when converting or validating the data.”

• Why JSONL works: In JSONL, each line is treated as a separate record. The ingestion service can parse each line individually, allowing successful ingestion.

Example:

✅ JSONL (works):

{"_id":"/profile/0001","personID":"000000000001","person":{"name":{"firstName":"Luis"}},"personalEmail":{"address":"user@example.com"}}

❌ Standard JSON (fails):

{ "_id": "/profile/0001", "personID": "000000000001", "person": { "name": { "firstName": "Luis" } }, "personalEmail": { "address": "user@example.com" } }

Recommendation:

Always use JSONL format for batch ingestion to Profile-enabled datasets in AEP. Each line represents a single record, ensuring that the ingestion parser can handle the data correctly.

References:

https://jsonlines.org/

Thanks,
Giriprasath B

​@OmarGo2 Batch data ingestion in AEP does not support multi-line json via UI upload. Incase you are ingesting through Batch Ingestion API and using multiline json, you can set “ismultilineJson=true”.  https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/batch/troubleshooting 

Hi ​@OmarGo2, 

Were you able to resolve this query with the help of the provided solutions, or do you still need further assistance? Please let us know. If any of the answers were helpful in moving you closer to a resolution, even partially, we encourage you to mark the one that helped the most as the 'Best Answer'.

Thank you!