Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Name:
interface
Value:
Amplify has re-imagined the way frontend developers build fullstack applications. Develop and deploy without the hassle.

Page updated Apr 29, 2024

Set up Amplify REST API

The Amplify API category provides an interface for making requests to your backend. The Amplify CLI deploys REST APIs and handlers using Amazon API Gateway and AWS Lambda.

Goal

To setup and configure your application with Amplify API to make requests to your API Gateway and trigger the lambda function using authorization provided by Amplify Auth.

Prerequisites

Make sure you have completed the below steps:

Configure API

To start provisioning API resources in the backend, go to your project directory and execute the command:

amplify add api

Enter the following when prompted:

? Please select from one of the below mentioned services:
`REST`
? Provide a friendly name for your resource to be used as a label for this category in the project:
`todoApi`
? Provide a path (e.g., /book/{isbn}):
`/todo`
? Choose a Lambda source
`Create a new Lambda function`
? Provide the AWS Lambda function name:
`todoFunction`
? Choose the function runtime that you want to use:
`NodeJS`
? Choose the function template that you want to use:
`Serverless ExpressJS function (Integration with API Gateway)`
? Do you want to access other resources created in this project from your Lambda function?
`No`
? Do you want to invoke this function on a recurring schedule?
`No`
? Do you want to edit the local lambda function now?
`No`
? Restrict API access
`No`
? Do you want to add another path?
`No`

To push your changes to the cloud, execute the command:

amplify push

Upon completion, amplifyconfiguration.json should be updated to reference provisioned backend storage resources. Note that this file should already be a part of your project if you followed the Project setup walkthrough.

Install Amplify Libraries

Use the package manager of your choice to install the amplify JS library. For example, with npm:

npm install aws-amplify

If you are using yarn:

yarn add aws-amplify

Initialize Amplify API

To initialize the Amplify API category you need to configure Amplify with Amplify.configure().

Import and load the configuration file in your app. It's recommended you add the Amplify configuration step to your app's root entry point. For example index.js in React or main.ts in Angular.

import { Amplify } from 'aws-amplify';
import amplifyconfig from './amplifyconfiguration.json';
Amplify.configure(amplifyconfig);

Make sure you call Amplify.configure as early as possible in your application’s life-cycle. A missing configuration or NoCredentials error is thrown if Amplify.configure has not been called before other Amplify JavaScript APIs. Review the Library Not Configured Troubleshooting guide for possible causes of this issue.

Make a POST Request

Send a POST request with a JSON body.

import { post } from 'aws-amplify/api';
async function postTodo() {
try {
const restOperation = post({
apiName: 'todoApi',
path: '/todo',
options: {
body: {
message: 'Mow the lawn'
}
}
});
const { body } = await restOperation.response;
const response = await body.json();
console.log('POST call succeeded');
console.log(response);
} catch (e) {
console.log('POST call failed: ', JSON.parse(e.response.body));
}
}

To navigate to your backend, go to the API Gateway console and select the API. The name of the API corresponds to the friendly name of the resource to be used as a label you specified earlier in the CLI steps.

Next steps

Congratulations! You've made a call to your API Gateway and triggered your Lambda function. Check out the following links to see other Amplify API use cases: