canonical: https://jentic.com/apis/interzoid.com/interzoid-state-data-standardization-api # Interzoid State Data Standardization API The Interzoid State Data Standardization API converts a US state name or Canadian province name in any common form into its two-letter abbreviation. It exists to clean inconsistent state values in inbound data - full names, abbreviations with periods, mixed case, common misspellings - into a single normalized form suitable for joins, filters, and downstream queries. The single GET endpoint returns the abbreviation alongside the original input so the caller can update records in place. ## For AI agents Standardize a US state or Canadian province name to its two-letter abbreviation so an agent can clean inbound data, build reliable joins, or filter on a normalized state column. ## Scope Does not validate full street addresses, geocode locations, or standardize country names - use for converting US state and Canadian province names to two-letter abbreviations only. ## Capabilities - Convert a free-text state name like 'California' or 'Calif.' to the two-letter abbreviation 'CA' - Standardize a Canadian province name to its two-letter abbreviation for reliable filtering - Clean a state column on an inbound CSV before loading it into a warehouse - Normalize state values across two source systems before joining on State as a key - Reject rows whose state value cannot be resolved by checking the Code field on the response ## Use cases ### CSV State Column Cleanup Normalize the state column in an inbound CSV so that variations like 'California', 'Calif.', and 'CA' all resolve to 'CA'. The State Data Standardization API takes one state value at a time, which works well inside a row-by-row ingestion script. Once standardized, the column can serve as a join key against territory or tax tables. Example prompt: For each row in a 1,000-row contacts CSV, call /getstateabbreviation with state set to the row's State value and overwrite the State column with the returned Abbreviation. ### Pre-Join Normalization Before joining two datasets on a State column, run each side through the standardization API so that mismatches caused by inconsistent state spelling do not produce false negatives. The API accepts US states and Canadian provinces, which removes the need to maintain a custom lookup table. The returned Abbreviation is the value to use for the join. Example prompt: For every distinct State value across two source tables, call /getstateabbreviation and write the returned Abbreviation into a normalized join key column on each side. ### Form Submission Hygiene Validate and normalize the state field on a web form before persisting the submission. The API resolves common misspellings and short forms, so a user who types 'Calif' still produces a clean 'CA' record in storage. A 400 response indicates the input could not be resolved, which can be returned to the user as a soft validation error. Example prompt: On form submit, call /getstateabbreviation with state set to the user input and reject the submission if the API returns a 400 status. ### Agent-Driven Address Cleansing via Jentic An AI data-quality agent uses Jentic to call the Interzoid State Data Standardization API as part of an address-cleansing routine that runs nightly over a contacts table. The agent reads the Abbreviation field, writes it back, and logs any rows that failed to resolve. Through Jentic the Interzoid license key is held in the credential vault and never enters the agent context. Example prompt: Use Jentic to search for 'standardize a US state name to its two-letter abbreviation', load /getstateabbreviation, and execute it for each contacts row to update the State column overnight. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/getstateabbreviation` | Convert a US state or Canadian province name to its two-letter abbreviation | ## Key resources - **State Data Standardization** — GET endpoint that accepts a US state or Canadian province name in free-text form and returns the two-letter Abbreviation. ## Why Jentic - **Setup:** Wiring the Interzoid State Data Standardization API by hand means obtaining a license key, appending it as a license query parameter on each call to /getstateabbreviation, and handling the request plumbing yourself. Through Jentic you install once, import this API from the API Directory, store the license key once, and your agent calls it. - **Permission scoping:** This API exposes a single read-only GET /getstateabbreviation operation that takes a state or province name in the query, with no resource id in the URL path, so scoping is at the operation level: you limit the agent to the abbreviation lookup it needs. It only normalizes a name and writes nothing, so there is no destructive operation to include. - **Credential handling:** Your Interzoid license key is stored once, encrypted, by your own Jentic One instance and injected as the license parameter at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'standardize a US state name to its two-letter abbreviation', and Jentic returns the State Data Standardization operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Smarty US ZIP Code** — US zip code validation that returns city, state, and zip combinations, useful alongside state standardization for full address hygiene. - **Interzoid Zip Code Detailed Info API** — Returns city, state, latitude, and longitude for a US zip code, helpful for cross-checking standardized state values. - **Interzoid Get Address Match Similarity Key API** — Generates similarity keys for postal addresses, often run after state standardization in a deduplication pipeline. ## FAQ ### What authentication does the Interzoid State Data Standardization API use? The API uses an Interzoid license key passed as the required `license` query parameter on /getstateabbreviation. Through Jentic the license key is held in the credential vault and injected at execution time, so the raw key never enters the agent context. ### Does this API cover Canadian provinces as well as US states? Yes. /getstateabbreviation resolves both US state names and Canadian province names to two-letter abbreviations, so a single endpoint can normalize cross-border address data. ### What are the rate limits for the Interzoid State Data Standardization API? The OpenAPI spec does not declare a numeric rate limit. Each successful call decrements a credit balance returned in the Credits response field, and a 402 status is returned when credits are exhausted. Refer to interzoid.com for current per-license-tier throughput. ### How do I standardize a state value through Jentic? Install the SDK with `pip install jentic`, search for 'standardize a US state name to its two-letter abbreviation', load /getstateabbreviation, and execute it with state set to the value to clean. The Abbreviation field is the value to write back. ### What happens when the state value cannot be resolved? The API returns a 400 status with no Abbreviation when the supplied state cannot be matched to a US state or Canadian province. Agents typically flag the row for manual review rather than retry. ### Does the API perform full address validation? No. /getstateabbreviation only standardizes the state component. For full street-and-zip validation, use a dedicated address-validation API such as Smarty's US Autocomplete or US ZIP Code services. ### Can I limit what my agent is allowed to do with the Interzoid State Data Standardization API? Yes. This API exposes a single read-only operation, GET /getstateabbreviation, which takes a state or province name and returns its two-letter abbreviation, so scoping happens at the operation level. Because you run Jentic One yourself, your own rules decide that your agent can call only this abbreviation lookup and use only the license key you have stored. There is no destructive or write operation to expose, since the endpoint only normalizes a name and changes nothing on Interzoid's side.