My team is having issues accessing the API endpoints. Did something change?

Hi Ryan, nothing has changed on our end and the endpoint seems to be accessible now. Could you please confirm the user you are making the call with?

What user info do you need?

the email username that is making the call

ok, I see that the user is an admin and should be able to make the call. I also see that there are no API access tokens created in the org. I would suggest creating the access tokens and then use that to authenticate: https://www.gooddata.com/docs/cloud/manage-organization/user-token/ Could you try this and let us know how the user gets on?

So Syrus made his own PAT and ended up still getting the same error.

The PAT was generated via the web console, let me know if there is anything else you need me to do differently.

Hello team, allow me to jump in here while my colleague is outside his business hours. Thank you for your patience while we investigated this. I believe the issue is related to the workspace ID used in your request. The request was being sent to:

<https://reporting.laivly.cloud/api/v1/entities/workspaces/intouchcx/workspaceDataFilterSettings>

This returned a 404 error because the workspace ID

intouchcx

does not exist. After checking your environment, I confirmed that the correct workspace ID for the workspace is

*tenant-intouchcx-v3*.

After updating the URL to use this ID, the request succeeded and returned a 200 OK. Please try updating your request to use the correct workspace ID and try again. In this case the endpoint should be https://reporting.laivly.cloud/api/v1/entities/workspaces/tenant-intouchcx-v3/workspaceDataFilterSettings You can also refer to our documentation here for more guidance on this. Let us know if this works.

Thanks @Yvonne Changamuka I overlooked that change when working with the WDFs, much appreciated