Geocoding

We had a couple of general questions, we are using the geocoding address autocomplete and address validation/verification.

We are using this API - The cloud saas precisely api for verify for example: https://api.cloud.precisely.com/v1/verify

For address autocomplete - I see that the TPS rate limit the document says 120 requests per second, that seems a low limit for a typeahead style search.   Just want to verify, is that correct?  I guess companies have to debounce from the front-end.

We were reviewing the other api "precisely api.precisely.com", we are not using that and using the api.cloud.precisely, in that other API, we could see a dashboard for number of transactions that might match our spending or credits.  We do not see that in the data integrity suite geocoding, is there a dashboard in the way to track api usage?

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification?

------------------------------
Berlin Brown
Primerica, Inc.
------------------------------

Yes, the Transaction Per Second (TPS) limit for autocomplete is 120, and you are correct that debouncing must be implemented on the front end. Note that the Autocomplete service is session-based, not only keystroke-based. Therefore, one request corresponds to one complete session. Refer to the X-Transaction-Id for details on implementing the Autocomplete Service.

Documentation weblink - https://help.cloud.precisely.com/r/t/1009843844/2025-11-18/Precisely-Data-Integrity-Suite/disapi/Latest/en-US/Data-Integrity-Suite-APIs/Address-Autocomplete

------------------------------
Neena Priyanka
*Precisely Software Inc.
Noida India ]

Original Message:
Sent: 12-15-2025 11:05
From: Berlin Brown
Subject: Just signed up for data integrity suite geocoding, couple of general questions

We had a couple of general questions, we are using the geocoding address autocomplete and address validation/verification.

We are using this API - The cloud saas precisely api for verify for example: https://api.cloud.precisely.com/v1/verify

For address autocomplete - I see that the TPS rate limit the document says 120 requests per second, that seems a low limit for a typeahead style search.   Just want to verify, is that correct?  I guess companies have to debounce from the front-end.

We were reviewing the other api "precisely api.precisely.com", we are not using that and using the api.cloud.precisely, in that other API, we could see a dashboard for number of transactions that might match our spending or credits.  We do not see that in the data integrity suite geocoding, is there a dashboard in the way to track api usage?

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification?

------------------------------
Berlin Brown
Primerica, Inc.
------------------------------

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification? - We generally see a new address in our system once it is recognized by the official postal authority (USPS, Canada Post, etc.), which we refresh in our datasets via monthly releases. Even if the house was built yesterday, the address often exists in postal records prior to completion. However, while the address might be verifiable shortly after our monthly update, the spatial precision (geocoding) matures over time-moving from a general area centroid to a specific rooftop coordinate as spatial vendors catch up.

Yes, the Transaction Per Second (TPS) limit for autocomplete is 120, and you are correct that debouncing must be implemented on the front end. Note that the Autocomplete service is session-based, not only keystroke-based. Therefore, one request corresponds to one complete session. Refer to the X-Transaction-Id for details on implementing the Autocomplete Service.

Documentation weblink - https://help.cloud.precisely.com/r/t/1009843844/2025-11-18/Precisely-Data-Integrity-Suite/disapi/Latest/en-US/Data-Integrity-Suite-APIs/Address-Autocomplete

------------------------------
Neena Priyanka
*Precisely Software Inc.
Noida India ]

Original Message:
Sent: 12-15-2025 11:05
From: Berlin Brown
Subject: Just signed up for data integrity suite geocoding, couple of general questions

We had a couple of general questions, we are using the geocoding address autocomplete and address validation/verification.

We are using this API - The cloud saas precisely api for verify for example: https://api.cloud.precisely.com/v1/verify

For address autocomplete - I see that the TPS rate limit the document says 120 requests per second, that seems a low limit for a typeahead style search.   Just want to verify, is that correct?  I guess companies have to debounce from the front-end.

We were reviewing the other api "precisely api.precisely.com", we are not using that and using the api.cloud.precisely, in that other API, we could see a dashboard for number of transactions that might match our spending or credits.  We do not see that in the data integrity suite geocoding, is there a dashboard in the way to track api usage?

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification?

------------------------------
Berlin Brown
Primerica, Inc.
------------------------------

Thanks for the information.    Couple more questions, hope we can continue within this thread.

Do you support a public API to do a health check or check the status of the geocoding apis are up?  Or maybe the host?

I see this is available as 200 response: https://api.cloud.precisely.com/healthz

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification? - We generally see a new address in our system once it is recognized by the official postal authority (USPS, Canada Post, etc.), which we refresh in our datasets via monthly releases. Even if the house was built yesterday, the address often exists in postal records prior to completion. However, while the address might be verifiable shortly after our monthly update, the spatial precision (geocoding) matures over time-moving from a general area centroid to a specific rooftop coordinate as spatial vendors catch up.

Yes, the Transaction Per Second (TPS) limit for autocomplete is 120, and you are correct that debouncing must be implemented on the front end. Note that the Autocomplete service is session-based, not only keystroke-based. Therefore, one request corresponds to one complete session. Refer to the X-Transaction-Id for details on implementing the Autocomplete Service.

Documentation weblink - https://help.cloud.precisely.com/r/t/1009843844/2025-11-18/Precisely-Data-Integrity-Suite/disapi/Latest/en-US/Data-Integrity-Suite-APIs/Address-Autocomplete

------------------------------
Neena Priyanka
*Precisely Software Inc.
Noida India ]

Original Message:
Sent: 12-15-2025 11:05
From: Berlin Brown
Subject: Just signed up for data integrity suite geocoding, couple of general questions

We had a couple of general questions, we are using the geocoding address autocomplete and address validation/verification.

We are using this API - The cloud saas precisely api for verify for example: https://api.cloud.precisely.com/v1/verify

For address autocomplete - I see that the TPS rate limit the document says 120 requests per second, that seems a low limit for a typeahead style search.   Just want to verify, is that correct?  I guess companies have to debounce from the front-end.

We were reviewing the other api "precisely api.precisely.com", we are not using that and using the api.cloud.precisely, in that other API, we could see a dashboard for number of transactions that might match our spending or credits.  We do not see that in the data integrity suite geocoding, is there a dashboard in the way to track api usage?

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification?

------------------------------
Berlin Brown
Primerica, Inc.
------------------------------

Thanks for the information.    Couple more questions, hope we can continue within this thread.

Do you support a public API to do a health check or check the status of the geocoding apis are up?  Or maybe the host?

I see this is available as 200 response: https://api.cloud.precisely.com/healthz

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification? - We generally see a new address in our system once it is recognized by the official postal authority (USPS, Canada Post, etc.), which we refresh in our datasets via monthly releases. Even if the house was built yesterday, the address often exists in postal records prior to completion. However, while the address might be verifiable shortly after our monthly update, the spatial precision (geocoding) matures over time-moving from a general area centroid to a specific rooftop coordinate as spatial vendors catch up.

Yes, the Transaction Per Second (TPS) limit for autocomplete is 120, and you are correct that debouncing must be implemented on the front end. Note that the Autocomplete service is session-based, not only keystroke-based. Therefore, one request corresponds to one complete session. Refer to the X-Transaction-Id for details on implementing the Autocomplete Service.

Documentation weblink - https://help.cloud.precisely.com/r/t/1009843844/2025-11-18/Precisely-Data-Integrity-Suite/disapi/Latest/en-US/Data-Integrity-Suite-APIs/Address-Autocomplete

------------------------------
Neena Priyanka
*Precisely Software Inc.
Noida India ]

Original Message:
Sent: 12-15-2025 11:05
From: Berlin Brown
Subject: Just signed up for data integrity suite geocoding, couple of general questions

We had a couple of general questions, we are using the geocoding address autocomplete and address validation/verification.

We are using this API - The cloud saas precisely api for verify for example: https://api.cloud.precisely.com/v1/verify

For address autocomplete - I see that the TPS rate limit the document says 120 requests per second, that seems a low limit for a typeahead style search.   Just want to verify, is that correct?  I guess companies have to debounce from the front-end.

We were reviewing the other api "precisely api.precisely.com", we are not using that and using the api.cloud.precisely, in that other API, we could see a dashboard for number of transactions that might match our spending or credits.  We do not see that in the data integrity suite geocoding, is there a dashboard in the way to track api usage?

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification?

------------------------------
Berlin Brown
Primerica, Inc.
------------------------------

Thanks for the information.    Couple more questions, hope we can continue within this thread.

Do you support a public API to do a health check or check the status of the geocoding apis are up?  Or maybe the host?

I see this is available as 200 response: https://api.cloud.precisely.com/healthz

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification? - We generally see a new address in our system once it is recognized by the official postal authority (USPS, Canada Post, etc.), which we refresh in our datasets via monthly releases. Even if the house was built yesterday, the address often exists in postal records prior to completion. However, while the address might be verifiable shortly after our monthly update, the spatial precision (geocoding) matures over time-moving from a general area centroid to a specific rooftop coordinate as spatial vendors catch up.

Yes, the Transaction Per Second (TPS) limit for autocomplete is 120, and you are correct that debouncing must be implemented on the front end. Note that the Autocomplete service is session-based, not only keystroke-based. Therefore, one request corresponds to one complete session. Refer to the X-Transaction-Id for details on implementing the Autocomplete Service.

Documentation weblink - https://help.cloud.precisely.com/r/t/1009843844/2025-11-18/Precisely-Data-Integrity-Suite/disapi/Latest/en-US/Data-Integrity-Suite-APIs/Address-Autocomplete

------------------------------
Neena Priyanka
*Precisely Software Inc.
Noida India ]

Original Message:
Sent: 12-15-2025 11:05
From: Berlin Brown
Subject: Just signed up for data integrity suite geocoding, couple of general questions

We had a couple of general questions, we are using the geocoding address autocomplete and address validation/verification.

We are using this API - The cloud saas precisely api for verify for example: https://api.cloud.precisely.com/v1/verify

For address autocomplete - I see that the TPS rate limit the document says 120 requests per second, that seems a low limit for a typeahead style search.   Just want to verify, is that correct?  I guess companies have to debounce from the front-end.

We were reviewing the other api "precisely api.precisely.com", we are not using that and using the api.cloud.precisely, in that other API, we could see a dashboard for number of transactions that might match our spending or credits.  We do not see that in the data integrity suite geocoding, is there a dashboard in the way to track api usage?

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification?

------------------------------
Berlin Brown
Primerica, Inc.
------------------------------

Actually two more questions

Does it make sense to "parse together the request for input" for geocoding address verification or use the other properties.  Will the result be the same?
E.g. this

https://api.cloud.precisely.com/v1/verify

{
  "preferences": {
    "maxResults": 4,
    "returnAllInfo": false,
    "matchMode": "",
    "customPreferences": {
      "ADDRESS_CASING": "PROPER"
    }
  },
  "addresses": [
    {
      "addressId": "1",
      "addressLines": [
        "476 5th Ave"
      ],
      "country": "USA",
      "admin1": "NY",
      "city": "New York",
      "postalCode": "10018",
      "postalCodeExt": ""
      
    }
  ]
}

...

or only parse together under addresslines

..

Also, another question, what is normally the release schedule for the API?  When changes are out?  breaking changes?

Thanks for the information.    Couple more questions, hope we can continue within this thread.

Do you support a public API to do a health check or check the status of the geocoding apis are up?  Or maybe the host?

I see this is available as 200 response: https://api.cloud.precisely.com/healthz

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification? - We generally see a new address in our system once it is recognized by the official postal authority (USPS, Canada Post, etc.), which we refresh in our datasets via monthly releases. Even if the house was built yesterday, the address often exists in postal records prior to completion. However, while the address might be verifiable shortly after our monthly update, the spatial precision (geocoding) matures over time-moving from a general area centroid to a specific rooftop coordinate as spatial vendors catch up.

Yes, the Transaction Per Second (TPS) limit for autocomplete is 120, and you are correct that debouncing must be implemented on the front end. Note that the Autocomplete service is session-based, not only keystroke-based. Therefore, one request corresponds to one complete session. Refer to the X-Transaction-Id for details on implementing the Autocomplete Service.

Documentation weblink - https://help.cloud.precisely.com/r/t/1009843844/2025-11-18/Precisely-Data-Integrity-Suite/disapi/Latest/en-US/Data-Integrity-Suite-APIs/Address-Autocomplete

------------------------------
Neena Priyanka
*Precisely Software Inc.
Noida India ]

Original Message:
Sent: 12-15-2025 11:05
From: Berlin Brown
Subject: Just signed up for data integrity suite geocoding, couple of general questions

We had a couple of general questions, we are using the geocoding address autocomplete and address validation/verification.

We are using this API - The cloud saas precisely api for verify for example: https://api.cloud.precisely.com/v1/verify

For address autocomplete - I see that the TPS rate limit the document says 120 requests per second, that seems a low limit for a typeahead style search.   Just want to verify, is that correct?  I guess companies have to debounce from the front-end.

We were reviewing the other api "precisely api.precisely.com", we are not using that and using the api.cloud.precisely, in that other API, we could see a dashboard for number of transactions that might match our spending or credits.  We do not see that in the data integrity suite geocoding, is there a dashboard in the way to track api usage?

Do you know the algorithm or approach for updating new addresses, if a house is built yesterday, what time will it appear for address validation or verification?

------------------------------
Berlin Brown
Primerica, Inc.
------------------------------