Struggling accesses Timezone API - I use the same ...
# gooddata-cloud
d
Struggling accesses Timezone API - I use the same token as with other API calls that do work - and I'm the admin. api call urls
Copy code
<https://reporting.laivly.cloud/api/v1/entities/workspaces/$workspaceid/workspaceSettings/timezone>
<https://reporting.laivly.cloud/api/v1/entities/organizationSettings/timezone>
Getting this result
Copy code
{
  "detail": "The requested endpoint does not exist or you do not have permission to access it.",
  "status": 404,
  "title": "Not Found",
  "traceId": "cc6a4ecedf305ae529c84acd0a198ea5"
}
f
Hey Doug, have you checked if the endpoints are valid? For instance,
/api/v1/entities/organizationSettings/timezone
is not a default endpoint. You would need to use the timezone setting’s ID to access it via APIs. Please check the Get Organization entities endpoint via GET to get a list of all organization Settings and check the ID you used for the timezone setting; then, use it for the
/api/v1/entities/organizationSettings/{id}
endpoint. Let me know if that doesn’t work out!
d
Well, looks like we aren't using them, I don't see it in the list
only see "ACTIVE_COLOR_PALETTE" "WHITE_LABELING" "ACTIVE_THEME"
f
You’re right, I will highlight this article for an update. The examples there use a default
timezone
id, but it first needs to be created. And when that is done, you can set any ID (or no ID at all, so it will be auto-generated) and use it as part of the endpoint moving forward. Usually there will only be 1 timezone setting per workspace/domain, so you might as well call it
timezone
and use that. Since you are not seeing the setting on your end, that means it needs to be created. The article you linked explains how to do that in the section Configure Time Zones.
d
We have updated our timestamps @Francisco Antunes to 2024-07-11T173617.685+00:00 something like this, but we still are not getting any changes 😕