AWS Amplify REST API cannot find the API

Question

I'm playing with AWS Amplify since I've to introduce some of its feature in a legacy application that has no framework (no React, no Angular: just vanilla JS).

I used successfully the Auth module so I recreated a simple sign up/in/out strategy. What I want now is to call a REST API, using REST API module. So I created an API using API Gateway PetStore example and I would interact with it.

So I created the configuration:

import Amplify from '@aws-amplify/core';

Amplify.configure({
    Auth: {
       ...
    },
    API: {
        endpoints: [
            {
                name: "PetStore", // name of the API in API Gateway console
                endpoint: "https://XXX.execute-api.eu-central-1.amazonaws.com/dev",
                region: "eu-central-1",
                paths: ['/']
            }
        ]
    }
});

and somewhere else:

import Api from '@aws-amplify/api-rest'; 

Api.get('PetStore', '/pets', {})
   .then(response => {
       console.log(response)
   }).catch(error => {
       console.log(error);
   });

But, when executed, I get always the same error:

API PetStore does not exist

Any idea? Remember that:

API Already exist
I don't want to use Amplify CLI to create AWS resources

Isaac I9 · Answer 1 · 2021-03-09T15:28:55.930

8

I'd like to add that @Deiv was correct to suggest API.configure(), this worked for me. After trying amplify pull and amplify push I still received the error API <api-name> does not exist.

So my code now looks like this:

import Amplify, { API } from 'aws-amplify';
import awsconfig from './aws-exports';

Amplify.configure(awsconfig);
API.configure(awsconfig);

I am using npm package: aws-amplify 3.3.21

edited Mar 09 '21 at 15:28

answered Mar 03 '21 at 16:35

Isaac I9

139
2
7

score 3 · Answer 2 · answered Jan 10 '21 at 02:53

I had this same issue and I managed to resolve it by configuring the exports on the "Api" object directly:

API.configure(aws_exports);

Previously it worked for me with just setting it on Amplify.configure, but it seems a newer version of Amplify requires it on the sub module itself.

Some more bits and pieces can be found here in this long-standing issue (in which the same issue popped up for Auth, but I applied the same to both in my case and it fixed it): https://github.com/aws-amplify/amplify-js/issues/4315

score 2 · Answer 3 · answered Mar 15 '21 at 06:20

You need to call API.configure() after Amplify.configure is called, or else your API setup won't be applied, hence it returns API PetStore does not exist

import Amplify, { API } from 'aws-amplify'; // this part depends on which Amplify you are using. but make sure to import API


Amplify.configure({
    Auth: {
       ...
    },
    API: {
        endpoints: [
            {
                name: "PetStore", // name of the API in API Gateway console
                endpoint: "https://XXX.execute-api.eu-central-1.amazonaws.com/dev",
                region: "eu-central-1",
                paths: ['/']
            }
        ]
    }
});

// Call this 
API.configure(); // no awsconfig required as you have set your own

score 0 · Answer 4 · answered Feb 12 '21 at 09:00

We changed the version of aws-amplify from 3 back to a previous version "aws-amplify": "^2.2.2" in package.json and that resolved it.

Think version 3 broke the manual configuration of aws-amplify.

Try changing the version to a previous version you know worked.

NeG · Answer 5 · 2023-04-10T08:52:24.093

I might be replying on an old thread but I am also facing the similar issue with aws amplify REST API. So for the error API does not exist, I put the below Amplify.configure in index.js file of the JavaScript project and it worked.

Amplify.configure({
    Auth: {
       ...
    },
    API: {
        endpoints: [
            {
                name: "PetStore", // name of the API in API Gateway console
                endpoint: "https://XXX.execute-api.eu-central-1.amazonaws.com/dev",
                region: "eu-central-1",
                paths: ['/']
            }
        ]
    }
});

Hope this will help someone.

score -1 · Answer 6 · answered Jan 08 '21 at 11:57

-1

API * does not exist usually means you haven't pushed the REST API you created. If you can't use amplify push have you manually created and amplify API through the console?

answered Jan 08 '21 at 11:57

pnewhook

4,048
2
31
49

AWS Amplify REST API cannot find the API

6 Answers6