OFAC API Frequently Asked Questions
Effective date: January 1, 2014
I have an API key, what are the next steps?
You're now able to use the RESTful screening API by passing your API key and search parameters. You should fully read and understand the documentation before developing your integration framework.
If you have any questions about the API or your account, please contact us.
How do I update my payment method?
To update your subscription payment method please visit our payment update page. You will need your API key. If you don't have your API key, please contact us at contact@ofac-api.com. When you update your payment information, it will become the default method for future invoices, and no further invoices will be charged against your prior payment method.
If you have any questions about the API or your account, please contact us.
I intend to use the API within a commercial product, is that allowed?
In short, yes. The API is intended for use with any product or organization that has KYC, CDD or any other compliance obligation, regardless of business model. However, direct resale of the API is not permitted through the standard plans listed. To discuss resale options, please contact us at contact@ofac-api.com
Are there any usage or frequency limitations for the API service?
Since 2014, OFAC-API.com has proudly offer free screening services to our global community of users, however we ask that you remain considerate and make API requests as sparingly as possible to limit overhead. It is recommend that requests are limited 240 calls per month (8 calls per day). If you require a larger call volume, please consider our subscription options.
What is Overage Protection
Overage Protection insures clients against excessive overage fees in the event of rapidly expanding business, unintentional checks, etc. Overage fees will not exceed $100 per month for plans that include Overage Protection, regardless of the amount of overage. In situations where excessive overage is frequent, we will reach out to you to discuss options.
Why are OFAC API search results are different than other searches online?
While the Depart of Treasury released an outline of the search algorithm developed for treas.gov, they did not release the algorithm itself. The OFAC-API search algorithm follows the fuzzy logic guidelines laid out on treasury.gov here to perform an OFAC compliant name search. One goal of OFAC-API is to limit the number of false positives, while remaining as flexible as possible. In many cases, we find the OFAC-API search results to be more accurate than those of sanctionssearch.ofac.treas.gov. If you come across a search discrepancy, please bring it to our attention at contact@ofac-api.com.
How does OFAC API determine a match?
OFAC API does not determine SDN name matches, it assigns a score to each SDN entry and returns those entries to you for review. It is up to you to determine if a returned SDN entry is a match. You can find more information about how to determine if an SDN entry is a match here.
How does OFAC API assign a match score?
OFAC API uses a blended Jaro Winkler and Soundex comparison algorithm, taking into account partial perfect matches, differences in name length and total name parts. The search was developed in collaboration with the Department of the Treasury.
Need more help?
Do you need more help understanding, developing or implementing your organizations compliance strategy? We are experts on the various
regulatory guidelines and are able to offer valuable guidance and consulting services.
Integration and technology consulting is also available.
Please contact us if you'd like to review your options.