This section describes how to get tax rate for coordinates using the GeoTAX API service. You may want to try it out with a Free Trial Account.
This method will consume credits.
- HTTP Request
- URL Composition
- Base URL: https://api.cloud.precisely.com
- GeoTAX Service:/v1/geo-tax/location/batch
- Supported Methods: POST only
- Rate Limit (Transactions per second): 50
- Input Fields Each request to the API service requires a few
parameters, all of which are listed below. All requests require a Bearer
token, that can be generated using your account's key-secret. To produce a
bearer token for an API request, the generated key-secret combinations are
used . The generated token is valid for 3600sec (1 hour) and then it needs
to be regenerated.
The data should be encoded as a JSON array where each element in the array is a JSON object with field names identical to those in the input/output fields listed below.
- URL Composition
| Parameter | Description | Example Value |
|---|---|---|
preferences |
Options supported by the GeoTAX Service which include a variety of settings categorized into output, geocoding, matching, and custom. Some of the preferences under geocoding include, defaultBufferWidth, latLongOffset, and many more. |
Set a different default buffer width. Default= The default integer value is 0. |
|
|
List of coordinates of the location. |
Latitude: latitude of the location
|
Below is a sample request for GeoTAX by batch location end point:
{
"preferences": {
"output": {
"taxDistrict": "NONE",
"salesTaxRateType": "NONE",
"outputCasing": "UPPER",
"taxCrossReferenceKey": "NONE",
"usePTC": "NO",
"userBoundary": "NO"
},
"geocoding": {
"defaultBufferWidth": 0,
"latLongOffset": "NONE",
"squeeze": "NO",
"latLongAltFormat": "DecimalSign",
"usePointData": "NO"
},
"matching": {
"matchMode": "CLOSE",
"useGeoTaxAuxiliaryFile": "NO",
"useUserAuxiliaryFile": "NO"
}
},
"locations": [
{
"longitude": -98.401796,
"latitude": 34.688726
},
{
"longitude": -92.9036,
"latitude": 34.8192
}
]
}