See Find your API key.
Your API key may have been compromised or you may have lost track of an automated process. If you've invested and determined that's the case, here's how to fix it:
Set up IP Filtering on your API Key to ensure that only servers of known IP addresses can call the API
- go to your Manage API Keys, under the "Actions" column clic on the 3 vertical-dots beside your API Key and select "Restrict by IP" and add the know IP address authorized to use the API.
Deactivate your current API Key and generate a new key (see Find your API key), and keep it hidden... keep it safe.
The REACH API servers log all inbound API requests into a database and these are then reported "as is" in the usage page. If any discrepancy in are seen in the numbers it may be often caused by duplicate API requests sent to our servers. We recommend reviewing the code used for the API calls and suggest activating outbound logs to have a clear report on the outbound calls.
Note: REACH API logs are based on US Pacific TIme and NOT UTC; this may also be the cause of the discrepancy in numbers.
Yes, the REACH APIs accepts SHA1, SHA256 and MD5 inputs. For details see Hashed Input Support.
Versium REACH APIs currently support only US Data.
Each API uses the match codes (fuzzy and precise matching) and data sources (broad or only the most reliable) that make the most sense for what you're trying to accomplish. This difference can result in the same inputs returning lots of matches or none, depending on the API call.
Response Time varies and is directly dependent on the API payload.
What is reported on the APIs Response Time page are the average response time for each API. Depending on their payload (i.e. the data that the API is provided with as input) the response time will vary.
Developers may use the rcfg_max_time parameter to "force" the API a maximum allowed run time (in seconds). Please see each API guide for details.
Updated 3 months ago