What the response contains
Try 11, 62, and 21 and use the returned fields to identify the right record.
Fields worth checking
- State
- Associated cities
BrasilAPI DDD
State · Associated cities
Live lookup
Type a real query, scan the cards and confirm the key details before opening the full source.
Quick examples
What the response actually contains
The route receives a two-digit DDD and returns state and cities. A lookup for 62, for example, returns GO and a list of municipalities associated with that numbering area. The DDD is the input to the request, not a field that proves where a particular phone is.
- Use state as the federation-unit code supplied by the source.
- Read cities as an associated list, not as a precise location for every number.
- Keep the queried DDD alongside the response if the application needs to show what was looked up.
How to use the lookup well
Send only the two digits and validate the format before calling the route. The result can support form normalisation, support routing, and grouped reporting when a broad numbering-area reference is enough.
- Test a known code such as 11, 21, or 62 before connecting it to a form.
- Handle an invalid code or a network failure without discarding the entered phone number.
- Store the source response separately from a person’s declared address.
Limits that matter
A DDD is not proof of residence, identity, carrier, or current physical presence. Important decisions about service availability, billing, eligibility, or contact details need the relevant address and confirmation from the person or organisation involved.
- Do not assign a municipality to a caller from the DDD alone.
- Do not use the list to identify the owner of a number.
- Review the official documentation before depending on coverage in a critical flow.