Error: "Failed to read request" 400 in Applications Manager Request API (startDate format)

Products

• Automic Applications Manager

Issue/Introduction

When attempting to execute a job via the Automic Automation Request API, the API returns an HTTP 400 "Bad Request" error with the detail: "Failed to read request". This often occurs when passing date parameters.

Symptoms:

• The API returns HTTP Status 400.
• The response body indicates: {"type":"about:blank","title":"Bad Request","status":400,"detail":"Failed to read request"}.
• The startDate parameter includes a time zone offset (e.g., -04:00).

Environment

• Applications Manager Request API
  
  
• Using api-server.jar from unreleased version 9.6.3

Cause

The Request API expects the startDate format to strictly follow the required timestamp schema without an explicit time zone offset appended to the string. If a client-side library automatically appends an offset (e.g., -04:00), the API fails to parse the request.

Resolution

Remove the time zone offset from the startDate string in your API request body.

Correct Format Example: "startDate":"2026-08-03T14:51:54.2055015"

Incorrect Format Example: "startDate":"2026-08-03T14:51:54.2055015-04:00"

1. Ensure your application logic strips the offset before sending the JSON payload to the /api/request endpoint.
2. Validate the request body schema before execution.

If the issue persists, ensure you are referencing the official AM REST API Documentation. If you need further assistance, please contact Broadcom Support.

Additional Information

The unreleased 9.6.3 api-server.jar can be found below:
Error: 500 Internal Server Error in History or Backlog APIs - Applications Manager