---
title: "missing_request_parameter"
description: "Error cause: missing_request_parameter"
canonical: "https://studio.inttegro.dev/e/c-missing_request_parameter"
format: inttegro-machine-docs/v1
language: "cURL"
reader_profile: optional
reader_manifest: "https://studio.inttegro.dev/machine/curl/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: 358
model_token_report: "https://studio.inttegro.dev/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 972
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Error cause: missing_request_parameter This cURL representation preserves HTTP paths and JSON wire names.

### Five questions

#### Q1. When should the reader use missing_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/curl/e/f-change_request_parameters.md) and [invalid_request_parameter](https://studio.inttegro.dev/machine/curl/e/c-invalid_request_parameter.md) when those concerns enter scope.

## Document content

# missing\_request\_parameter

Error cause indicating required request parameters were not provided.

## What this means

The Inttegro API endpoint you called requires one or more parameters that were not included in your request. Each endpoint has a defined set of required parameters that must be present for the operation to proceed—when any of these mandatory fields are absent, you'll receive this error cause. For example, paying for an order without providing the `order_id` parameter, or connecting a financial account without specifying the required account details.

The error detail field will identify exactly which parameter is missing, allowing you to add it to your request before retrying. This differs from `invalid_request_parameter` where the parameter is provided but its value doesn't meet validation requirements. Missing parameter errors are permanent failures that always require modifying your request to include the required fields—the Inttegro API cannot proceed with incomplete information.

## Example error response

```json
{
  "error": {
    "type": "invalid_request_parameter",
    "cause": "missing_request_parameter",
    "code": "1672",
    "message": "required parameter missing",
    "detail": "The `order_id` parameter is required but was not provided.",
    "fix_code": "change_request_parameters",
    "url": "https://studio.inttegro.com/e/1672"
  }
}
```

## Related errors

- [invalid\_request\_parameter](https://studio.inttegro.dev/machine/curl/e/c-invalid_request_parameter.md) - Parameter provided but invalid
- [change\_request\_parameters](https://studio.inttegro.dev/machine/curl/e/f-change_request_parameters.md) - Fix code for this error