Access to fetch at ‘https://boostfloral.discourse.group/categories.json?’ from origin ‘http://localhost:3000’ has been blocked by CORS policy: Request header field API-key is not allowed by Access-Control-Allow-Headers in preflight response. Getting the above issue when I am trying to call the discourse APIs. I have already added an SSL certificate to my servers. I am adding the CORS options present on my admin panel but still getting this issue. Has anyone faced something like this and could help me what is the way out of this???

[תמונה] Fahad Aslam: field API-key is not allowed Is it a User API Key? If I’m not wrong, it should be User-Api-Key.

Now I am getting the below response. Access to fetch at ‘https://boostfloral.discourse.group/latest.json?order=default&ascending=false’ from origin ‘http://localhost:3000’ has been blocked by CORS policy: Request header field api-username is not allowed by Access-Control-Allow-Headers in preflight response.

If you’re trying to consume the Admin API (as opposed User API), the header fields required are Api-Key and Api-Username.

[תמונה] Fahad Aslam: Request header field api-username is not allowed by Access-Control-Allow-Headers in preflight response. I think for public Javascript clients, admin api is not allowed (sadly, this complicates everything, I know!) But you’re going to have to use User API keys specification instead. For me, I’m still trying to figure out how as well. I just want to pull a .json response that’s publicly available.

[תמונה] Al-Gassim Sharaf Addin: I just want to pull a .json response that’s publicly available. If it’s public then configuring CORS should suffice and you should not need to bother with API keys at all.

Yes, thanks! This has been solved for me here: Using JavaScript fetch to get publicly available page from Discourse into an external site (Discourse API) - #2 by pfaffman @fahadaslam98 as @RGJ said, if the CORS is properly configured then removing the API keys from the headers should work, :+1:

בעיה בגישה ל-APIs של Discourse מאפליקציית React

מפתח

RGJ (Richard - Communiteq) 9 באפריל,‏ 2023,‏ 7:03am 7

If it’s public then configuring CORS should suffice and you should not need to bother with API keys at all.

נושא		תגובות	צפיות
CORS policy configuration with React Product Support	3	1886	8 באפריל,‏ 2023
CORS error accessing API from javascript application Development	11	4173	9 באפריל,‏ 2023
API CORS Headers Incorrect Product Support	10	3228	6 ביולי,‏ 2020
Authenticating using API keys when accessing API through fetch Development rest-api	4	1604	28 בנובמבר,‏ 2019
Acess-Control-Allow-Headers CORS Error with API after updating discourse Product Support	9	3499	22 ביולי,‏ 2020

בעיה בגישה ל-APIs של Discourse מאפליקציית React

נושאים קשורים