Doug Creighton
08/08/2024, 7:19 PM<https://reporting.laivly.cloud/api/v1/entities/workspaces/$workspaceid/workspaceSettings/timezone>
<https://reporting.laivly.cloud/api/v1/entities/organizationSettings/timezone>
Getting this result
{
"detail": "The requested endpoint does not exist or you do not have permission to access it.",
"status": 404,
"title": "Not Found",
"traceId": "cc6a4ecedf305ae529c84acd0a198ea5"
}
Francisco Antunes
08/08/2024, 7:36 PM/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!Doug Creighton
08/08/2024, 7:37 PMDoug Creighton
08/08/2024, 7:40 PMDoug Creighton
08/08/2024, 7:42 PMFrancisco Antunes
08/08/2024, 7:44 PMtimezone
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.Doug Creighton
09/10/2024, 6:42 PM