cool, thanks! for now, just testing things out, no major problems with that part.

looking at the

init

method now. what

apiDomain

refers to? in my case of adding ST to a Lambda function should this API domain be the URL of the Lambda func itself?

Yes. That is, what domain does the frontend use to reach the lambda function?

in case of netlify / nextJS, the apiDomain is equal to the websiteDomain.

but what about

apiDomain

when `init`ing the backend SDK?

it should be the same value as what's on the frontend

you can essentially copy the same object

okay, perfect.

that you used on the frontend

for appInfo

then what about

websiteDomain

if the frontend app is still in development and not deployed anywhere yet?

so it should be the same as whats on your frontend. If frontend is on http://localhost:8080 at the moment, then the value here should be "http://localhost:8080"

you can use environment variables i'm assuming to determine if the function is running in dev or prod env. Based on that, you can set this value or something else.

true.

so when I deploy the frontend app and get it a real domain name, I will just have to change them again or via the env vars.

exactly. It's best to do i with env vars

yeah, for sure.

so that when ur developing locally, it will pick the right value

then what about

apiBasePath

? what does it point to? and is it relevant for the backend part only or also for the front-?

> then what about apiBasePath? So can you give me an example of how you would reach an API from the frontend?

like if it's a different domain compared to the frontend, you can set it to

/auth

(which is the default). This means all the APIs we expose via the nodeSDK will be in

/auth/*

.

If the api domain is the same as the website domain (as is the case for netlify), then the api is usually reachable via a path like

/.netlify/functions/*

. So we can make the apiBasePath something like

/.netlify/functions/api

or

/.netlify/functions/auth

So if you are not sure, you can give me an example of what an api call looks like from your frontend, and I can tell you what the values should be

yes, imagine the frontend calls the backend with

https://blah-blah.execute-api.blah-blah.amazonaws.com/stage/my-endpoint

Cool. So

apiDomain

should be

https://blah-blah.execute-api.blah-blah.amazonaws.com

and the

apiBasePath

should be

/stage/auth

. This means the node sdk will expose a bunch of APIs on

https://blah-blah.execute-api.blah-blah.amazonaws.com/stage/auth/*

And based on the name, I assume you will also have something like

/prod/api-endpoint

so the

apiBasePath

can be modified too based on env vars

yes, exactly.

oh man, that's great! thanks a lot! you see, if it wasn't for you many of those things would still be unclear compared to just following the docs.

yeaaa.. clearly there is a lot of work needed in the docs! haha.. we are working on it a lot though