1. Align use cases with fundraising goals
Have you conducted a review of your organization’s use cases for an API?
Consider if you have upcoming projects, initiatives, and goals that require going beyond what is available in a standalone platform.
Have there been developments that suggest the time is right to leverage an API?
If you are starting a new campaign, expanding your team, experiencing an increase in incoming gifts, or have a long-term fundraising strategy in place, it may be time to consider upgrading to an API.
2. Technical support and infrastructure
Does your Tech Team have the capacity and capability to support an API?
Determine if your technical team has bandwidth to install the API and to potentially place calls for the team or to create an interface for the prospect research team to use.
Will the API work with your systems, including data warehousing?
The API should be compatible with most systems, but it’s important to ensure that there are no issues with accessibility and that data and API workflows meet your security requirements.
3. Assess CRM data quality and completeness
Is the data in your CRM out of date or incomplete?
One of the ways an API can add value is by filling gaps in your CRM, including regional coverage, contact details, net worth indicators, and key relationship connections.
Do you have a recurring need for screening?
APIs enable ongoing screening to quickly identify new opportunities, including daily or weekly review of new gifts as they come in.
4. Leadership team readiness
Do you have a champion, and support from your leadership?
Early alignment with key decision-makers helps ensure that the strategic value of API integration is understood and prioritized across the organization.
Are you aware of the approvals required for adding an API?
Map out the review and approval process in advance to avoid delays. Identify the stakeholders who need to be involved early in the process, including legal, technical, data security, procurement, and leadership, so each team understands its role, requirements, and timeline for evaluation.
How to use this institutional API readiness checklist
Use this Institutional API Readiness Checklist as a shared evaluation tool across departments. It can guide conversations around investment timing, workflow planning, and long-term data strategy.
5. Choose the right partner
Do you have a clear idea of the data and functionality of the API?
Review developer documentation and request details on structure, functionality, limitations, and example calls.
Are you asking the right questions to determine if the organization is a good fit?
Best practices include asking who the potential partner has worked with, and if they will enable your tech team to run comprehensive testing.