---
title: "change_request_parameters"
description: "Fix code: change_request_parameters"
canonical: "https://studio.inttegro.dev/e/f-change_request_parameters"
format: inttegro-machine-docs/v1
language: "Python"
sdk_version: "v14.1.1"
reader_profile: optional
reader_manifest: "https://studio.inttegro.dev/machine/python/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: 1016
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Fix code: change_request_parameters This Python representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

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

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

## Document content

# change\_request\_parameters

Fix code indicating the request parameters are invalid and must be corrected before retrying.

## What this means

The Inttegro API has determined that your request contains one or more parameter values that don't meet validation requirements, and you must modify these parameters before retrying the operation. This is the most actionable fix code you'll encounter—it tells you that the solution is in your hands and requires changing your request. The error detail field will specify exactly which parameter is problematic and what constraint it violated, giving you clear direction on what to fix. For example, if you paginate through orders with `page_number: 15` and receive this fix code, you need to change the page number to a value between 1 and 10 before retrying.

Similarly, if paying for an order fails because the provided `payment_method_id` does not exist, use a valid payment method ID. Unlike `repeat_same_request`, this fix code means the request will continue to fail until you correct the parameter identified by the 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

- [invalid\_request\_parameter](https://studio.inttegro.dev/machine/python/e/t-invalid_request_parameter.md) - Error type often paired with this fix code
- [missing\_request\_parameter](https://studio.inttegro.dev/machine/python/e/c-missing_request_parameter.md) - Related validation cause