Current timezone
Setup current timezone
- application/json
Request Body required
- current_timezone string
Possible values: [
UTC−12:00
,UTC−11:00
,UTC−10:00
,UTC−09:30
,UTC−09:00
,UTC−08:00
,UTC−07:00
,UTC−06:00
,UTC−05:00
,UTC−04:00
,UTC−03:30
,UTC−03:00
,UTC−02:00
,UTC−01:00
,UTC±00:00
,UTC+01:00
,UTC+02:00
,UTC+03:00
,UTC+03:30
,UTC+04:00
,UTC+04:30
,UTC+05:00
,UTC+05:30
,UTC+05:45
,UTC+06:00
,UTC+06:30
,UTC+07:00
,UTC+08:00
,UTC+08:45
,UTC+09:00
,UTC+09:30
,UTC+10:00
,UTC+10:30
,UTC+11:00
,UTC+12:00
,UTC+12:45
,UTC+13:00
,UTC+14:00
]Timezone model
- 200
- 400
- 401
OK
Bad Request
- application/json
- Schema
- Example (from schema)
Schema
error object
Describes the base error user might get
code stringPossible values: [
invalid_authentication
,permission_denied
,not_valid
,system_error
]Error code
message stringError message
data object
Did not pass validation parameters. Can be represented as an object, which can include field names, arrays, query parameters etc.
param stringDescribes the parameter that did not pass a validation
{
"error": {
"code": "not_valid",
"message": "Data validation error",
"data": {
"param": "must be an string"
}
}
}
Please log in
- application/json
- Schema
- Example (from schema)
- Example
Schema
error object
Describes the base error user might get
code stringPossible values: [
invalid_authentication
,permission_denied
,not_valid
,system_error
]Error code
message stringError message
data object
Did not pass validation parameters. Can be represented as an object, which can include field names, arrays, query parameters etc.
param stringDescribes the parameter that did not pass a validation
{
"error": {
"code": "not_valid",
"message": "Data validation error",
"data": {
"param": "must be an string"
}
}
}
{
"error": {
"code": "invalid_authentication",
"message": "Log In"
}
}