/v1/table endpoint is not working (including repo example)

[sslee811]

The table fetching feature hasn't been working for a few days. Even the example provided in this repository (https://notion-api.splitbee.io/v1/table/20720198ca7a4e1b92af0a007d3b45a4) is not functioning.
On the other hand, 'load page' is working normally. Could you please look into this?

[dev-alto]

Experiencing this issue too. I disabled all caching, reforked the main branch to a new Vercel deployment, and am even using the public hosted version to no avail.

[amenglong]

Here the same problem. Any help is more than welcomed. Thanks!

[deevannaveed]

@sslee811 here is the reason, since I am using a Lambda so I had to update my Lambda code, hope someone can open a PR or you can do it for yourself in the worker code.

[steakscience]

@deevannaveed If you already have the working fix for this repo, do you mind submitting a PR?

[tankotun]

@steakscience you can do it on your own. create a vercel project from https://github.com/splitbee/notion-api-worker.git repo. it will create a private repo on your github account. go to that github repo, edit project on codespace.

open /src/routes/table.ts file, add // @ts-nocheck to the top, and add ?.value end of the line 34.

commit and push. go back to vercel project and redeploy it. then change the api url in your code with the vercel project url.

it works well.

[sslee811]

@steakscience you can do it on your own. create a vercel project from https://github.com/splitbee/notion-api-worker.git repo. it will create a private repo on your github account. go to that github repo, edit project on codespace.

open /src/routes/table.ts file, add // @ts-nocheck to the top, and add ?.value end of the line 34.

commit and push. go back to vercel project and redeploy it. then change the api url in your code with the vercel project url.

it works well.

Applying those changes resolved the problem. I appreciate your help.