remoteFetchAsync not working

[hbfreed]

I need help with making HTTP requests in Blocks:

1. Regular fetch() fails with CORS errors as (more or less) expected in Blocks
2. In my original extension script, I used remoteFetchAsync which worked fine for handling CORS issues
3. However, when I try to use remoteFetchAsync in Blocks, it seems to not exist at all

I've thoroughly checked the @airtable/blocks SDK, since the docs don't seem to say anything about this for blocks, (it has the "Scripting Extension Only" tag).

Questions for the Airtable team:

1. What is the current, supported way to make HTTP requests from Blocks?
2. If there isn't one, why not? And when will this be fixed?
3. Can you explain why remoteFetchAsync works in extensions but isn't available in Blocks?

Thanks for any help, and happy holidays!

[lisa52smith]

It sounds like you're facing a common issue with CORS errors when trying to make HTTP requests in Airtable Blocks, no ...](https://community.airtable.com/t5/development-apis/basic-http-requests-in-blocks-cors-error-with-fet...). Since **remoteFetchAsync** is not available in Blocks, you might consider using a workaround such as enabling CORS on your API server or using a browser extension to bypass CORS restrictions.