Every funder API integration in MCA Pilot follows the same setup flow: request credentials, configure the funder in Development, submit a test deal, and switch to Production after the funder confirms the test.
MCA Pilot currently supports API integrations with 19 funders. Jump to the guide for yours in the numbered list at the bottom of this article.
Standard setup steps
Email the funder’s API contact to request credentials and development access.
In MCA Pilot, go to the Funders page and create or click into the funder.
Open the Submission Method tab and click Edit in the top right.
Choose API Integration as the Submission Method.
Select the funder for API Funder and Development for API Environment.
Enter the credentials in the API Key field. The exact format depends on the funder—see the funder-specific table below.
Submit a test deal that includes the required info and documents for that funder.
If the test succeeds, copy the response (or the Application Name, if the funder uses one) and email it back to the funder to request production access.
Once the funder sends production credentials, return to the funder settings, enter the new credentials, and change API Environment to Production.
Each funder requires slightly different fields and documents. The funder-specific guides below list exactly what a test deal needs for that integration.
Funder contacts and credential formats
Click a funder's contact below to open a pre-filled email (with Victor Fteha CC'd) requesting API credentials.
Funder | Contact | API Key format |
Single API key | ||
Six comma-separated values: Consumer Key, Client Secret, Unique General Email, Unique General Password, Unique Partner API Key, Sales Rep Email | ||
Single API key | ||
UAT key for Development; production key for Production | ||
Client ID and client secret, comma-separated | ||
Token (partner email and rep name are optional), comma-separated | ||
Single API key | ||
Email and API key, comma-separated | ||
Single API key | ||
Username and password, comma-separated | ||
Username, password, client ID, client secret, comma-separated | ||
Client ID and client secret, comma-separated | ||
Single API key | ||
Single API key | ||
API key, username, password, comma-separated | ||
Username, password, partner ID, broker number, comma-separated | ||
Username and password, comma-separated | ||
Single API key | ||
Username and password, comma-separated |
Verify a test submission
After you submit a test deal, check the submission on the deal page:
Hover over the submission and click Check Status to refresh the latest response from the funder.
Some funders also show an Open in Funder button that opens the submission directly in the funder’s portal.
If the submission is successful, copy the response details and send them to the funder contact to request production access.
Switch to production
Wait for the funder to issue production credentials.
Return to the funder’s funder page in MCA Pilot.
Open Submission Method → Edit.
Replace the API Key with the production credentials.
Change API Environment to Production and save.
Fix a production key swap
If you entered a production key but submissions still fail or route to the test environment, the environment dropdown or the key format is usually the cause.
In MCA Pilot, go to Funders, open the funder, and click the Submission Method tab.
Click Edit and confirm API Environment is set to Production, not Development.
Confirm the API Key matches the exact production format the funder sent. Some integrations require commas, multiple values, or a specific order.
Click Save.
Submit a test deal and hover over the submission to click View error if it still fails.
If the funder uses different keys for test and production (for example, Credibly UAT vs production keys), the entire key string must be replaced; editing part of the old key will fail.
Fix a failed submission
If a test submission errors, hover over the submission and click View error to see the exact message. Fix the missing or invalid fields on the deal and resubmit.
Common causes of test failures are missing required fields, invalid phone numbers, or missing documents. Each funder guide lists the required fields and formats for that integration.
Fix stalled submissions and credential issues
If a deal won't submit or the status stops updating, check credentials and the production handoff first.
Missing or invalid credentials
Missing or invalid credentials
If the API key field is empty or the funder returns an authentication error, request fresh credentials from the funder's API contact listed in the table above. Paste the new key into the API Key field in Funders > Submission Method > Edit, and make sure the format matches the funder-specific entry exactly.
Production handoff is not complete
Production handoff is not complete
If submissions fail after switching to Production, confirm the funder approved your test submission and issued production credentials. In Funders > Submission Method > Edit, verify that API Environment is set to Production and the API Key contains the production credentials, not the development key. Some funders require the entire key string to be replaced; editing part of the old key will fail.
Submission is stuck or not updating
Submission is stuck or not updating
Hover over the submission and click Check Status to force a refresh from the funder. If the status still doesn't change, click View error to see the exact message, fix the missing or invalid fields on the deal, and resubmit.
All funder integration guides
Read the detailed guide for your funder for exact required fields, document types, and special notes: