---
title: "bad_request"
description: "Error type: bad_request"
canonical: "https://studio.inttegro.dev/e/t-bad_request"
format: inttegro-machine-docs/v1
language: "PHP"
sdk_version: "v14.1.1"
reader_profile: optional
reader_manifest: "https://studio.inttegro.dev/machine/php/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 357
model_token_report: "https://studio.inttegro.dev/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 930
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Error type: bad_request This PHP representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use bad_request?

Use this page as orientation before selecting the narrower guide or reference that owns the implementation contract.

#### Q2. What is authoritative on this page?

Use this page for orientation; follow its canonical SDK, guide, API, or MCP links for exact contracts.

#### Q3. What page-specific constraint matters most?

Use the page to choose a canonical next source instead of treating summary material as a complete implementation contract.

#### Q4. Can Inttegro MCP materially help with this task?

No catalog ability is sufficiently specific to recommend for this page. Use the documentation directly; consult the MCP catalog only if the task later requires governed live account context or a supported operation.

#### Q5. How should the reader verify the answer and continue?

Select the narrowest linked guide or reference, apply its stated completion condition, and verify against authoritative resource state when the task changes data. Continue with [authentication_failed](https://studio.inttegro.dev/machine/php/e/c-authentication_failed.md) and [invalid_request_parameter](https://studio.inttegro.dev/machine/php/e/t-invalid_request_parameter.md) when those concerns enter scope.

## Document content

# bad\_request

Error type constant indicating a malformed or invalid request.

## What this means

The request you sent doesn't meet the basic structural requirements for processing by the Inttegro API. This error occurs when the request itself is malformed—for example, invalid JSON syntax in the request body, missing required HTTP headers like `Content-Type: application/json`, or using an unsupported HTTP method for the endpoint. Unlike `invalid_request_parameter` which indicates problems with specific parameter values, `bad_request` signals that the Inttegro API couldn't even parse or understand your request structure.

If you're creating a new order and receive this error, check that your request body is valid JSON, you're using the POST method, and you've included the proper headers. This error type always requires fixing the request structure before retrying.

## Example error response

```json
{
  "error": {
    "type": "bad_request",
    "cause": "invalid_request_parameter",
    "code": "1293",
    "message": "malformed request body",
    "detail": "The request body contains invalid JSON syntax. Unable to parse the request.",
    "fix_code": "change_request_parameters",
    "url": "https://studio.inttegro.com/e/1293"
  }
}
```

## Related errors

- [invalid\_request\_parameter](https://studio.inttegro.dev/machine/php/e/t-invalid_request_parameter.md) - Specific parameter validation failures
- [authentication\_failed](https://studio.inttegro.dev/machine/php/e/c-authentication_failed.md) - Missing or invalid credentials