APIs.io Engineering Platform · Schema
PutIntegrationRequest
Sets up a method's integration.
APIs.ioEngineeringPlatform
Properties
| Name | Type | Description |
|---|---|---|
| type | object | |
| integrationHttpMethod | object | |
| uri | object | |
| connectionType | object | |
| connectionId | object | |
| credentials | object | |
| requestParameters | object | |
| requestTemplates | object | |
| passthroughBehavior | object | |
| cacheNamespace | object | |
| cacheKeyParameters | object | |
| contentHandling | object | |
| timeoutInMillis | object | |
| tlsConfig | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/PutIntegrationRequest",
"title": "PutIntegrationRequest",
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"allOf": [
{
"$ref": "#/components/schemas/IntegrationType"
},
{
"description": "Specifies a put integration input's type."
}
]
},
"integrationHttpMethod": {
"allOf": [
{
"$ref": "#/components/schemas/String"
},
{
"xml": {
"name": "httpMethod"
},
"description": "The HTTP method for the integration."
}
]
},
"uri": {
"allOf": [
{
"$ref": "#/components/schemas/String"
},
{
"description": "Specifies Uniform Resource Identifier (URI) of the integration endpoint. For HTTP or <code>HTTP_PROXY</code> integrations, the URI must be a fully formed, encoded HTTP(S) URL according to the RFC-3986 specification, for either standard integration, where <code>connectionType</code> is not <code>VPC_LINK</code>, or private integration, where <code>connectionType</code> is <code>VPC_LINK</code>. For a private HTTP integration, the URI is not used for routing. For <code>AWS</code> or <code>AWS_PROXY</code> integrations, the URI is of the form <code>arn:aws:apigateway:{region}:{subdomain.service|service}:path|action/{service_api</code>}. Here, {Region} is the API Gateway region (e.g., us-east-1); {service} is the name of the integrated Amazon Web Services service (e.g., s3); and {subdomain} is a designated subdomain supported by certain Amazon Web Services service for fast host-name lookup. action can be used for an Amazon Web Services service action-based API, using an Action={name}&{p1}={v1}&p2={v2}... query string. The ensuing {service_api} refers to a supported action {name} plus any required input parameters. Alternatively, path can be used for an Amazon Web Services service path-based API. The ensuing service_api refers to the path to an Amazon Web Services service resource, including the region of the integrated Amazon Web Services service, if applicable. For example, for integration with the S3 API of <code>GetObject</code>, the <code>uri</code> can be either <code>arn:aws:apigateway:us-west-2:s3:action/GetObject&Bucket={bucket}&Key={key}</code> or <code>arn:aws:apigateway:us-west-2:s3:path/{bucket}/{key}</code>."
}
]
},
"connectionType": {
"allOf": [
{
"$ref": "#/components/schemas/ConnectionType"
},
{
"description": "The type of the network connection to the integration endpoint. The valid value is <code>INTERNET</code> for connections through the public routable internet or <code>VPC_LINK</code> for private connections between API Gateway and a network load balancer in a VPC. The default value is <code>INTERNET</code>."
}
]
},
"connectionId": {
"allOf": [
{
"$ref": "#/components/schemas/String"
},
{
"description": "The ID of the VpcLink used for the integration. Specify this value only if you specify <code>VPC_LINK</code> as the connection type."
}
]
},
"credentials": {
"allOf": [
{
"$ref": "#/components/schemas/String"
},
{
"description": "Specifies whether credentials are required for a put integration."
}
]
},
"requestParameters": {
"allOf": [
{
"$ref": "#/components/schemas/MapOfStringToString"
},
{
"description": "A key-value map specifying request parameters that are passed from the method request to the back end. The key is an integration request parameter name and the associated value is a method request parameter value or static value that must be enclosed within single quotes and pre-encoded as required by the back end. The method request parameter value must match the pattern of <code>method.request.{location}.{name}</code>, where <code>location</code> is <code>querystring</code>, <code>path</code>, or <code>header</code> and <code>name</code> must be a valid and unique method request parameter name."
}
]
},
"requestTemplates": {
"allOf": [
{
"$ref": "#/components/schemas/MapOfStringToString"
},
{
"description": "Represents a map of Velocity templates that are applied on the request payload based on the value of the Content-Type header sent by the client. The content type value is the key in this map, and the template (as a String) is the value."
}
]
},
"passthroughBehavior": {
"allOf": [
{
"$ref": "#/components/schemas/String"
},
{
"description": "Specifies the pass-through behavior for incoming requests based on the Content-Type header in the request, and the available mapping templates specified as the <code>requestTemplates</code> property on the Integration resource. There are three valid values: <code>WHEN_NO_MATCH</code>, <code>WHEN_NO_TEMPLATES</code>, and <code>NEVER</code>. "
}
]
},
"cacheNamespace": {
"allOf": [
{
"$ref": "#/components/schemas/String"
},
{
"description": "Specifies a group of related cached parameters. By default, API Gateway uses the resource ID as the <code>cacheNamespace</code>. You can specify the same <code>cacheNamespace</code> across resources to return the same cached data for requests to different resources."
}
]
},
"cacheKeyParameters": {
"allOf": [
{
"$ref": "#/components/schemas/ListOfString"
},
{
"description": "A list of request parameters whose values API Gateway caches. To be valid values for <code>cacheKeyParameters</code>, these parameters must also be specified for Method <code>requestParameters</code>."
}
]
},
"contentHandling": {
"allOf": [
{
"$ref": "#/components/schemas/ContentHandlingStrategy"
},
{
"description": "<p>Specifies how to handle request payload content type conversions. Supported values are <code>CONVERT_TO_BINARY</code> and <code>CONVERT_TO_TEXT</code>, with the following behaviors:</p> <p>If this property is not defined, the request payload will be passed through from the method request to integration request without modification, provided that the <code>passthroughBehavior</code> is configured to support payload pass-through.</p>"
}
]
},
"timeoutInMillis": {
"allOf": [
{
"$ref": "#/components/schemas/NullableInteger"
},
{
"description": "Custom timeout between 50 and 29,000 milliseconds. The default value is 29,000 milliseconds or 29 seconds."
}
]
},
"tlsConfig": {
"$ref": "#/components/schemas/TlsConfig"
}
},
"description": "Sets up a method's integration."
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/apis-io-engineering-platform-putintegrationrequest"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.