GeoTAX

Determines tax jurisdiction and tax codes of given batch coordinates

This endpoint takes list of latitudes and longitudes as input and determines which tax jurisdiction given coordinates are located in, and which current tax codes apply.

post/v1/geo-tax/location/batch

Request

  • Base URL: https://api.cloud.precisely.com
  • URL: https://api.cloud.precisely.com/v1/geo-tax/location/batch
  • Auth: one of:
    • HTTP bearer
    • API key in header Authorization

Headers

X-Request-Idstring

The X-Request-Id header is optional but incredibly useful for developers. It serves as a unique identifier for requests within our system. When you encounter any problems with your requests, providing us with the X-Request-Id will enable us to pinpoint the specific request in question without the need for extensive manual searching. This means faster and more efficient troubleshooting. The maximum allowed length is 38 characters.

Request body

Example request

{
  "locations": [
    {
      "addressId": "1",
      "longitude": -98.401796,
      "latitude": 34.688726
    }
  ],
  "preferences": {
    "geocoding": {
      "latLongOffset": "NONE",
      "squeeze": "NO",
      "latLongAltFormat": "DecimalDirectional",
      "usePointData": "YES"
    },
    "matching": {
      "matchMode": "EXACT",
      "useGeoTaxAuxiliaryFile": "YES",
      "useUserAuxiliaryFile": "NO"
    },
    "output": {
      "taxDistrict": "SPD",
      "salesTaxRateType": "GENERAL",
      "outputCasing": "UPPER",
      "taxCrossReferenceKey": "VERTEX",
      "usePTC": "NO",
      "userBoundary": "NO"
    }
  }
}

Response

Tax Details Retrieved Successfully for batch locations

Changes

No recorded changes to this operation across all 1 revision of this API.