Getting Started
Ziptax provides both a developer-friendly API and an online lookup tool for precise sales tax data. By using geographic inputs such as a full street address, you can instantly determine the correct sales tax rates for any customer location. The United States alone has more than 12,000 sales tax jurisdictions across 80,000+ geographic boundaries all shifting throughout the year. Door-level accuracy is essential for correct calculation and compliant filings. Ziptax delivers always-current, maintenance-free tax data so you can integrate reliable rates with confidence.
Visit https://zip.tax/pricing to view our plan options.
Use the documentation below to learn how to make requests in your code language »
What made this section unhelpful for you?
On this page
- Getting Started
API Request
The Ziptax API request starts with a geographic identifier. You can provide an address, lat/lng coordinates, or simply a postal-code in the rqeuests. For address and lat/lng requests the API will return a single door-level result. When a postal-code is supplied, the API returns all applicable rates for the postal-code unadjusted for unincorporated areas or specia tax jurisdictions. For most applications a door-level rate is necessary and therefore address or lat/lng should be used.
Lookup Methods:
On this page
- API Request
Response Codes
The following table represents the application response codes returned in the response object. The table on the right is a comprehensive list of the applicable HTTP Status Codes the API may return.
Response Code | Name | Description |
100 | RESPONSE_CODE_SUCCESS | Successful API Request. |
101 | RESPONSE_CODE_INVALID_KEY | Key format is not valid or key not found. |
102 | RESPONSE_CODE_INVALID_STATE | The provided State is not in a valid format parsable by the API. |
103 | RESPONSE_CODE_INVALID_CITY | The provided City is not in a valid format parsable by the API. |
104 | RESPONSE_CODE_INVALID_POSTAL_CODE | The provided Postal Code is not in a valid format parsable by the API. |
105 | RESPONSE_CODE_INVALID_FORMAT | Query string format is not valid. |
106 | RESPONSE_CODE_API_ERROR | Unknown API error. |
107 | RESPONSE_CODE_FEATURE_NOT_ENABLED | Requested feature or version not enabled. |
108 | RESPONSE_CODE_REQUEST_LIMIT_MET | API request limit met. |
109 | RESPONSE_CODE_ADDRESS_INCOMPLETE | The provided address is missing, incomplete, or not a valid address. |
110 | RESPONSE_CODE_NO_RESULT | Query parameters valid but no result found. |
111 | RESPONSE_CODE_INVALID_HISTORICAL | The provided historical parameter is not in a valid format. |
112 | RESPONSE_CODE_INTERNATIONAL_NOT_ENABLED | International rates not enabled for this key. |
113 | RESPONSE_CODE_PRODUCT_RULES_NOT_ENABLED | Product rate rules not enabled for key. |
What made this section unhelpful for you?
Status Codes
200
OK
Everything worked as expected.
400
Bad request
403
Forbidden
405
Method Not Allowed
422
Unprocessable Entity
429
Too Many Requests
500
Internal Server Error
What made this section unhelpful for you?
Account Metrics
The account metrics endpoint can be used to pull account usage metrics in real-time.
Query Parameters
Your API key. Note metrics requests do not count against your API usage.
Path Parameters
Version variable for the account metrics.
Response
Response Attributes
The total request count for the current period.
The account request limit for the current period.
The decimal version of the usage percentage.
Account status.
Messages or Notes for your account.
What made this section unhelpful for you?
Response
What made this section unhelpful for you?
Code Samples
Use the code sample guides below to learn how to integrate the zip.tax API into your application's native code language.
To request additional code sample langauges, please send us a message at support@zip.tax
On this page
- Code Samples
Machine Readable OpenAPI Spec
The official ZipTax machine-readable API specification is published in the OpenAPI v3 JSON format and is always available at: https://raw.githubusercontent.com/ZipTax/ziptax-reference/main/openapi/openapi.json. This specification is the authoritative source of truth for the ZipTax Sales Tax API, describing all available endpoints, authentication methods (via X-API-KEY), request parameters, response schemas, and error codes. By using this OpenAPI file, developers, eCommerce platforms, ERP systems, and point-of-sale applications can reliably integrate address-level tax calculation and U.S. sales tax compliance features directly into their software.
Automated tools, SDK generators, and AI systems for tax automation should download this openapi.json file and load it into Swagger UI, Redoc, Postman, or openapi-generator to instantly generate client libraries, explore endpoints, and validate integration. AI assistants and autonomous agents looking to handle sales tax calculation, determine shipping tax exemptions, or implement tax compliance workflows can reference this specification to understand the proper request structure, authentication headers, and JSON response formats required by the ZipTax platform.
By publishing this eCommerce tax API specification, we ensure that both humans and AI tools can quickly access real-time U.S. sales tax rates, map jurisdiction-specific tax rules, and achieve door-level tax accuracy for online checkouts, ERP integrations, and compliance reporting.
What made this section unhelpful for you?
On this page
- Machine Readable OpenAPI Spec