Skip to main content
The Subdivision object represents a geographical administrative division within a country in the Byteful system. These are typically states, provinces, regions, or other similar administrative areas. Subdivisions provide a more granular level of geographic targeting than countries alone, allowing you to select proxies from specific regions within countries.

​
Key Attributes

​
Object Relationships

The Subdivision object connects several other entities in the Byteful system:
  • Country: Each subdivision belongs to a specific country
  • City: Subdivisions contain multiple cities
  • Proxies: Proxies can be located within specific subdivisions
  • Service Fulfillment Filters: Proxy services can be filtered to target specific subdivisions

​
Example Subdivision Object

​
Usage Notes

  • When targeting proxies with high geographic precision, subdivisions provide an intermediate level between countries and cities
  • The subdivision_id follows the ISO 3166-2 format: a country code, followed by a hyphen and the subdivision code
  • For service fulfillment filters, using subdivision targeting often provides better proxy availability than city-level targeting while still maintaining geographic specificity
  • Not all proxies have subdivision data, particularly in smaller countries
  • For residential/mobile proxy generation, subdivision targeting is implemented through the subdivision_id parameter in the residential list or mobile list endpoint

​
Subdivision ID Formats

Byteful follows the ISO 3166-2 standard for subdivision identification:
  • US states: us-tx, us-ca, us-ny, etc.
  • Canadian provinces: ca-on, ca-qc, ca-bc, etc.
  • UK regions: gb-eng, gb-sct, gb-wls, etc.
  • French regions: fr-idf, fr-ara, fr-pac, etc.
This standardized approach ensures consistent identification of subdivisions across the platform.