> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dncscrub.com/llms.txt
> Use this file to discover all available pages before exploring further.

# get_timezone_info Tool

> Get timezone and location information for phone numbers

The `get_timezone_info` tool returns timezone and location information for North American phone numbers. Use this to determine local time before calling.

## When to Use

* Determining the local time at a phone number's location
* Planning call schedules across multiple time zones
* Ensuring calls are made during appropriate hours

## Parameters

<ParamField body="phoneNumbers" type="string[]" required>
  List of 10-digit North American phone numbers (e.g., `["5039367187", "2125551234"]`).
</ParamField>

<ParamField body="overwriteTodaysTime" type="string">
  Optional ISO 8601 datetime to use instead of current time for DST calculations.
</ParamField>

<ParamField body="loginId" type="string">
  API key. Only required if not provided via the `x-dncscrub-api-key` HTTP header.
</ParamField>

## Response

<ResponseField name="success" type="boolean">
  Whether the API call succeeded.
</ResponseField>

<ResponseField name="results" type="array">
  Array of results, one per phone number.

  <Expandable title="result object">
    <ResponseField name="phone" type="string">
      The phone number checked.
    </ResponseField>

    <ResponseField name="timezone" type="string">
      Timezone name (e.g., `America/Los_Angeles`).
    </ResponseField>

    <ResponseField name="state" type="string">
      2-letter state/province code.
    </ResponseField>

    <ResponseField name="utcOffset" type="string">
      UTC offset string (e.g., `-08:00`).
    </ResponseField>

    <ResponseField name="utcOffsetMinutes" type="number">
      UTC offset in minutes.
    </ResponseField>

    <ResponseField name="hasDST" type="boolean">
      Whether this timezone observes daylight saving time.
    </ResponseField>

    <ResponseField name="dstStartDate" type="string | null">
      Next DST start date.
    </ResponseField>

    <ResponseField name="dstEndDate" type="string | null">
      Next DST end date.
    </ResponseField>

    <ResponseField name="lata" type="string">
      Local Access Transport Area code.
    </ResponseField>

    <ResponseField name="rateCenter" type="string">
      Rate center / LIR info.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="errorCode" type="string">
  Machine-readable error code (when failed).
</ResponseField>

<ResponseField name="errorMessage" type="string">
  Human-readable error description (when failed).
</ResponseField>

## Examples

<Tabs>
  <Tab title="Request">
    ```json theme={null}
    {
      "phoneNumbers": ["5039367187", "2125551234"]
    }
    ```
  </Tab>

  <Tab title="Response">
    ```json theme={null}
    {
      "success": true,
      "results": [
        {
          "phone": "5039367187",
          "timezone": "America/Los_Angeles",
          "state": "OR",
          "utcOffset": "-08:00",
          "utcOffsetMinutes": -480,
          "hasDST": true,
          "dstStartDate": "2024-03-10",
          "dstEndDate": "2024-11-03",
          "lata": "672",
          "rateCenter": "PORTLAND"
        },
        {
          "phone": "2125551234",
          "timezone": "America/New_York",
          "state": "NY",
          "utcOffset": "-05:00",
          "utcOffsetMinutes": -300,
          "hasDST": true,
          "dstStartDate": "2024-03-10",
          "dstEndDate": "2024-11-03",
          "lata": "132",
          "rateCenter": "NEW YORK"
        }
      ]
    }
    ```
  </Tab>
</Tabs>

## Usage Notes

* Batch multiple numbers in a single request for efficiency
* Use `utcOffsetMinutes` for programmatic time calculations
* DST dates help plan for time changes
* For real-time "can I call now?" checks, use `is_time_legal_to_call` instead