Bulk price list upload via REST API fails in pricing management due to payload size error

ERP Oracle Fusion Cloud
, , , , , , , ,
1

We’re automating price list updates in Oracle Fusion Cloud 22D using the REST API. Single price list entries upload successfully, but bulk uploads consistently fail with ‘Invalid JSON’ errors.

Our automation sends multiple price list entries in a single request, but the API rejects the payload structure. Manual single-item uploads through the same endpoint work perfectly, which suggests the payload format for bulk operations differs from what we’re sending.

The error occurs immediately upon submission - no partial processing happens. We’ve verified our JSON is valid using external validators, but clearly the API expects a different structure for array-based submissions versus individual items.

This is blocking our automated pricing updates for over 5,000 SKUs that need weekly synchronization from our external pricing system.

2

Can you share the exact JSON structure you’re sending for bulk uploads? The pricing API has specific requirements for array-based payloads. Are you wrapping your items array in a parent object with the correct attribute name?

3

SOLVED! The issue was indeed the payload structure mismatch between single and bulk operations. Here’s what fixed it:

Root Cause Analysis: The Oracle Fusion Pricing REST API requires different JSON structures for single versus bulk operations. While single items can be posted as standalone objects, bulk uploads MUST wrap the array in a parent object with a specific collection property.

Correct Bulk Upload Structure:

{
  "parts": [
    {"PriceListId": "PL001", "ItemNumber": "SKU-123", "Price": 99.99},
    {"PriceListId": "PL001", "ItemNumber": "SKU-124", "Price": 149.99}
  ]
}

Key Implementation Points:

  1. Payload Structure: The API expects an object with a ‘parts’ collection property (not a raw array). This is documented in the REST API schema but easy to miss.

  2. Single vs Bulk Pattern: Single-item POSTs work with bare objects because they use a different endpoint pattern. Bulk operations always require the collection wrapper.

  3. Batch Size Limits: Oracle recommends maximum 500 items per request for optimal performance. We implemented chunking logic to split our 5000 SKUs into batches of 300.

  4. Error Handling: The ‘Invalid JSON’ error was misleading - the JSON was technically valid, but structurally incorrect for the bulk endpoint. Always validate against the specific endpoint’s schema definition.

Working Solution: We modified our automation to:

  • Wrap all bulk uploads in the required {“parts”: […]} structure
  • Implement batch chunking with 300 items per request
  • Add retry logic with exponential backoff for rate limiting
  • Log individual item failures within successful batch responses

Processing time for 5000 SKUs dropped from manual entry (hours) to automated bulk upload (under 5 minutes). The automation now runs successfully in our weekly pricing sync job.

Documentation Reference: Oracle Fusion Cloud REST API Guide, Section 4.2.3 - Bulk Operations Payload Structure

4

Thanks for the pointer! I found the schema documentation. Going to test with the wrapped structure and report back.

5

Another thing to watch - make sure your batch size doesn’t exceed API limits. Some Fusion endpoints have maximum array sizes (often 500-1000 items). If you’re sending 5000 SKUs, you’ll need to chunk them into multiple requests anyway.

6

The issue is definitely the payload structure. Oracle Fusion REST APIs follow a consistent pattern where bulk operations require the collection to be nested under a specific property name. For pricing endpoints in 22D, you typically need something like {“PriceListItems”: […your array…]}. The exact property name varies by resource type, so verify against your specific endpoint’s schema definition. Also ensure you’re setting Content-Type to application/json and using POST method for creates.