Jurisdictions list
Exactjurisdictions_listDeterministic and authoritative — the canonical answer for this input.
List all jurisdictions of a given type. Valid types: country (192), state (50 US), territory (5 US), district (1 — DC), armed_forces_postal (3). Returns items sorted by code with count. Processing multiple inputs? Use `jurisdictions_list_batch` to do up to 5 in one call.
Parameters
typestringrequiredJurisdiction type to list. Valid values: country, state, territory, district, armed_forces_postal.
Call it
curl -X POST https://api.snipget.ai/v1/jurisdictions/list \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{"type":"country"}'The Batch tab sends up to 1000 inputs in one call via /v1/jurisdictions/list/batch.
FAQ
What does this do?
It returns every jurisdiction of one type in a single call: all 192 countries, all 50 US states, the territories, DC, or the armed-forces postal codes. Handy for building a dropdown or seeding a reference table without copy-pasting a list you might get wrong.
What types can I ask for?
One of: country, state, territory, district, or armed_forces_postal. The type field is required, and items come back sorted by code.
Is this the same data a model would just write out?
It is the maintained, authoritative list, so you do not risk a model dropping a country or inventing one. The count field (e.g. 192 for country) lets you confirm you got the whole set.
What do I get for each entry?
Each item is a record with code, name, iso_code, type, and parent_code, plus a top-level count and the type you asked for.
What if I ask for a type that does not exist?
Asking for something like province is rejected with an INVALID_INPUT error naming the five supported types, and rejected calls are not billed. On the batch endpoint only the bad type errors; valid sibling types still answer.