Serverless Developer Guide
• child resources - such as /users/PremiumUser to retrieve special types of Users
• path parameters – such as /users/{UserId} to retrieve a speciﬁc user by an identiﬁer like 
12345 or UserA
Resources must have an integration to connect the resource to a back-end endpoint:
• integration – connection to a Lambda function, HTTP endpoint, or AWS service action
The following diagram shows the components of a URL request: API Endpoint, Stage, and 
Resource.
• API Endpoint: The hostname for the API. Unless you designate a custom domain name, all APIs 
created using API Gateway will have this structure.
• Stage Name: An API deployment. You can deploy diﬀerent snapshots of your API to various 
stages, for example: “v2", "latest", "dev", "qa".
• Resource: The piece of your business logic provided by the request.
To create an REST API resource, you specify the resource path, then add a method with an API 
integration endpoint. You can then further conﬁgure the integration and test it in the console. 
The following screenshot shows an example REST API integration for a GET method for the /users 
resource.
After you are satisﬁed with your conﬁguration, you must deploy the API to a stage so it 
will become available to process requests.
Fundamentals 64