---
title: "invalid_request_parameter"
description: "Error type: invalid_request_parameter"
canonical: "https://studio.inttegro.dev/e/t-invalid_request_parameter"
format: inttegro-machine-docs/v1
language: "C#"
sdk_version: "v13.1.0"
reader_profile: optional
reader_manifest: "https://studio.inttegro.dev/machine/csharp/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: 367
model_token_report: "https://studio.inttegro.dev/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 962
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

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

### Five questions

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

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 [change_request_parameters](https://studio.inttegro.dev/machine/csharp/e/f-change_request_parameters.md) and [missing_request_parameter](https://studio.inttegro.dev/machine/csharp/e/c-missing_request_parameter.md) when those concerns enter scope.

## Document content

# invalid\_request\_parameter

Error type indicating the request failed due to invalid or incorrectly formatted parameters.

## What this means

The request structure is valid and parseable, but one or more parameters contain values that violate validation rules, format requirements, or business logic constraints. This is the most common error type you'll encounter when integrating with the Inttegro API. For example, paginating through orders with `page_number: 15` when the maximum is 10, or paying for an order with an unknown `payment_method_id`.

The error detail field will explain exactly which parameter is invalid and why, allowing you to correct the specific value before retrying. Unlike transient errors that resolve themselves, invalid parameter errors require you to modify your request—retrying the exact same request will always produce the same error.

## Example error response

```json
{
  "error": {
    "type": "invalid_request_parameter",
    "cause": "invalid_request_parameter",
    "code": "1564",
    "message": "page_number out of bounds",
    "detail": "The `page_number` value you provided, `15`, is out of bounds. It should be between 1 and 10 inclusive.",
    "fix_code": "change_request_parameters",
    "url": "https://studio.inttegro.com/e/1564"
  }
}
```

## Related errors

- [missing\_request\_parameter](https://studio.inttegro.dev/machine/csharp/e/c-missing_request_parameter.md) - Required parameter not provided
- [change\_request\_parameters](https://studio.inttegro.dev/machine/csharp/e/f-change_request_parameters.md) - Fix code for this error type