Understanding the Subdivision object and its role in the Ping Proxies API
Attribute | Type | Description |
---|---|---|
subdivision_id | string | Unique identifier for the subdivision (e.g., us-tx for Texas, USA) |
subdivision_name | string | Full name of the subdivision (e.g., Texas ) |
subdivision_alias | string | Alternative identifier or shorthand (e.g., us_tx ) |
country_id | string | ISO country code of the parent country (e.g., us ) |
Endpoint | Description |
---|---|
GET /public/user/subdivision/retrieve/{subdivision_id} | Retrieve a specific subdivision |
GET /public/user/subdivision/search | Search subdivisions with filters |
GET /public/user/city/search?subdivision_id={subdivision_id} | Find cities within a specific subdivision |
GET /public/user/proxy/search?subdivision_id={subdivision_id} | Find proxies in a specific subdivision |
subdivision_id
follows the ISO 3166-2 format: a country code, followed by a hyphen and the subdivision codesubdivision_id
parameter in the residential list endpointus-tx
, us-ca
, us-ny
, etc.ca-on
, ca-qc
, ca-bc
, etc.gb-eng
, gb-sct
, gb-wls
, etc.fr-idf
, fr-ara
, fr-pac
, etc.