REQUEST_INVALID - Pulse API

The request breaks a rule: a field is missing, unknown, or holds a value it can’t take.

Status	Retryable	Title
`400`	No	Invalid request

Common causes

The body isn’t a JSON object or a form the endpoint reads.
A field is missing, misspelled, of the wrong type, or out of range.
A query parameter or header isn’t one the endpoint takes.

What to do

Fix each field errors names (its pointer locates it in the body), then send the request again.

Example

{
  "type": "https://docs.runpulse.com/errors/request-invalid",
  "title": "Invalid request",
  "status": 400,
  "detail": "config.pages: unknown field",
  "instance": "urn:pulse:request:req-6f1c2a9e-3b7d-4c55-9a8e-2d4f0b1c7e93",
  "code": "REQUEST_INVALID",
  "request_id": "req-6f1c2a9e-3b7d-4c55-9a8e-2d4f0b1c7e93",
  "retryable": false,
  "errors": [
    {
      "field": "config.pages",
      "pointer": "#/config/pages",
      "issue": "unknown field"
    }
  ]
}

In API version 1 this was REQ_001, REQ_002, REQ_003, REQ_004, REQ_005, SCHEMA_001, INVALID_REQUEST.