Hi Team Could someone help checking why we are still getting CORS errors when this domain has already been whitelisted Access to XMLHttpRequest at 'https://learnamp.cloud.gooddata.com/api/v1/actions/workspaces/examplecompanya/resolveSettings' from origin 'https://examplecompanya.nas-demo.learnampdemo.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Even when a domain has been whitelisted in your CORS settings, there are a few things worth checking: Things to Verify 1. Confirm the exact domain is listed correctly Make sure the origin

https://examplecompanya.nas-demo.learnampdemo.com

is added exactly as it appears in your allowed origins list. A common mistake is a typo or missing/extra subdomain level. 2. Check your Organization ID in the API call If you configured CORS via the API, ensure you used your actual organization ID (not just

default

) in the endpoint URL. The correct format is:

https://<hostname>/api/v1/entities/admin/organizations/<orgID>

A 404 error is returned if the organization ID is incorrect. [CORS API endpoint] 3. Use PATCH, not PUT When updating allowed origins via the API, make sure you're using a

PATCH

request. Your request body should look like:

{
  "data": {
    "attributes": {
      "allowedOrigins": [
        "https://examplecompanya.nas-demo.learnampdemo.com"
      ]
    },
    "id": "<your_organization_id>",
    "type": "organization"
  }
}

[CORS setup docs] 4. Wildcard usage If you used a wildcard pattern (e.g.,

https://*.learnampdemo.com

), note that wildcards only match third-level and consecutive subdomains. Verify the pattern covers your specific subdomain structure. [CORS setup docs] 5. Verify via the UI You can double-check the current allowed origins list by going to your GoodData homepage → Developer settings → Cross-origin resource sharing (CORS) → Manage. This will show you exactly what is currently whitelisted. [CORS setup docs] If after checking all of the above the issue persists, I'd recommend opening a support ticket with GoodData directly, as this may require investigation on the server side. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.

please could we have someone checking this

Hey Jhonatan, We can certainly look further into this. It may not be a CORS error exactly. Could you provide some more details as to the steps you are taking before seeing this error?

it doesn't load any embedded visulisation object or editor, in this attempt I am trying to load an embedded dashboard this is the userID 62dc15e8-8068-4643-b352-48a67622b177 trying to load things for workspace ID examplecompanya