List time zone identifiers, optionally narrowed to one country

Overview

Time zone identifiers for the registration form's timezone picker, optionally narrowed to one country. Without country, the exact list RegisterRequest validates the timezone field against - the two can never disagree. With country, PHP's own per-country identifier list.

Controller: App\Http\Controllers\Api\V1\Public\CountryController::timezones()
Route name: api.v1.public.timezones.index

Authentication

Type: None (public endpoint)
Additional middleware: throttle:public. See docs/api/README.md §14.

Request

Method: GET
Path: /api/v1/public/timezones

Query parameters

Parameter	Type	Required	Default	Description
`country`	`string(2)`	No	none (returns every identifier)	ISO 3166-1 alpha-2 country code. Validated by `TimezonesRequest`

Example request

Response `200 OK`

Without country: every PHP timezone identifier, 419 at capture time (truncated to 3 below). With country=IT: exactly one entry, captured in full.

{
  "success": true,
  "status": "success",
  "message": "OK",
  "data": [
    { "value": "Europe/Rome", "label": "Europe/Rome" }
  ]
}

Without country (first 3 of 419 entries, alphabetical):

{
  "success": true,
  "status": "success",
  "message": "OK",
  "data": [
    { "value": "Africa/Abidjan", "label": "Africa/Abidjan" },
    { "value": "Africa/Accra", "label": "Africa/Accra" },
    { "value": "Africa/Addis_Ababa", "label": "Africa/Addis_Ababa" }
  ]
}

Response fields

Field	Type	Nullable	Always present	Description
`data[].value`	`string`	No	Yes	The identifier to send back as `timezone` at registration
`data[].label`	`string`	No	Yes	Identical to `value`. Kept as a separate key for the same `{value, label}` shape every other public lookup uses

Errors

`422 Unprocessable Entity` — validation

FormRequest validation, standard envelope. Two causes share this shape: wrong length and unrecognised code. Captured live for an unrecognised code:

{
  "success": false,
  "status": "error",
  "message": "Validation failed",
  "errors": {
    "country": ["Invalid country code"]
  }
}

`429 Too Many Requests`

Behind the dedicated public limiter (300 requests per minute, keyed by IP). No errors key.

{
  "success": false,
  "status": "error",
  "message": "Too many requests"
}

Notes

Unlike every other public endpoint's country parameter, this is the only one checked through App\Rules\CountryCode inside a FormRequest rather than an inline domain check - so its 422 always carries errors, never the bare domain-rejection shape.

New endpoint; utility had no equivalent.

List time zone identifiers, optionally narrowed to one country

Overview#

Authentication#

Request#

Query parameters#

Example request#

Response 200 OK#

Response fields#

Errors#

422 Unprocessable Entity — validation#

429 Too Many Requests#

Notes#

Request

Responses

Overview

Authentication

Request

Query parameters

Example request

Response `200 OK`

Response fields

Errors

`422 Unprocessable Entity` — validation

`429 Too Many Requests`

Notes