Which endpoints accept reference_id, and how do I correlate the ones that do not?

Last updated: September 22, 2026

reference_id lets you attach your own record identifier to a request and get it back on the webhook and on every fetch of the result. It is accepted on:

  • Business search

  • Person search

  • Web presence request

  • Industry prediction request

  • Criminal check

  • OFAC batch screening (per row)

It is not accepted on lien searches or docket searches. Those endpoints reject unrecognized fields rather than ignoring them, so sending it will fail the request.

For those two, correlate on the request ID that comes back when the search is accepted. Store it against your record before the webhook arrives, then match the webhook on it. For searches placed against a business or person you already hold, the response also carries that business or person ID, which gives you a second key.