Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

Method

import type { Method } from "https://aws-api.deno.dev/v0.3/services/apigateway.ts?docs=full";

TODO: Failed to render documentation: unhandled paragraph inner tag h4

interface Method {
apiKeyRequired?: boolean | null;
authorizationScopes?: string[] | null;
authorizationType?: string | null;
authorizerId?: string | null;
httpMethod?: string | null;
methodIntegration?: Integration | null;
methodResponses?: {
[key: string]: MethodResponse | null | undefined;
} | null;
operationName?: string | null;
requestModels?: {
[key: string]: string | null | undefined;
} | null;
requestParameters?: {
[key: string]: boolean | null | undefined;
} | null;
requestValidatorId?: string | null;
}

§Properties

§
apiKeyRequired?: boolean | null
[src]

A boolean flag specifying whether a valid "ApiKey" is required to invoke this method.

§
authorizationScopes?: string[] | null
[src]

A list of authorization scopes configured on the method. The scopes are used with a COGNITO_USER_POOLS authorizer to authorize the method invocation. The authorization works by matching the method scopes against the scopes parsed from the access token in the incoming request. The method invocation is authorized if any method scopes matches a claimed scope in the access token. Otherwise, the invocation is not authorized. When the method scope is configured, the client must provide an access token instead of an identity token for authorization purposes.

§
authorizationType?: string | null
[src]

The method's authorization type. Valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, CUSTOM for using a custom authorizer, or COGNITO_USER_POOLS for using a Cognito user pool.

§
authorizerId?: string | null
[src]

The identifier of an "Authorizer" to use on this method. The authorizationType must be CUSTOM.

§
httpMethod?: string | null
[src]

The method's HTTP verb.

§
methodIntegration?: Integration | null
[src]

TODO: Failed to render documentation: unhandled paragraph inner tag h4

§
methodResponses?: {
[key: string]: MethodResponse | null | undefined;
} | null
[src]

TODO: Failed to render documentation: unhandled paragraph inner tag h4

§
operationName?: string | null
[src]

A human-friendly operation identifier for the method. For example, you can assign the operationName of ListPets for the GET /pets method in the PetStore example.

§
requestModels?: {
[key: string]: string | null | undefined;
} | null
[src]

A key-value map specifying data schemas, represented by "Model" resources, (as the mapped value) of the request payloads of given content types (as the mapping key).

§
requestParameters?: {
[key: string]: boolean | null | undefined;
} | null
[src]

A key-value map defining required or optional method request parameters that can be accepted by API Gateway. A key is a method request parameter name matching the pattern of method.request.{location}.{name}, where location is querystring, path, or header and name is a valid and unique parameter name. The value associated with the key is a Boolean flag indicating whether the parameter is required (true) or optional (false). The method request parameter names defined here are available in "Integration" to be mapped to integration request parameters or templates.

§
requestValidatorId?: string | null
[src]

The identifier of a "RequestValidator" for request validation.