Skip to main content

OnDeck API Integration

Submit Deals instantly from MCA Pilot to OnDeck Capital

V
Written by Victor Fteha

When you submit to OnDeck via API, MCA Pilot submits the deal info, uploads the App and Banks, and brings the response into the deal — including declines and Offers.

For the standard API setup flow shared by all funder integrations, see Set up a funder API integration. This article covers OnDeck-specific credentials and the development-to-production handoff.

Hover over a submission to open it with Open in OnDeck, or click View error if the submission failed.

Before you begin

Request API credentials and development access from Jack Scafuri at [email protected] before you configure the funder in MCA Pilot.

Email Jack Scafuri at OnDeck to request API credentials (Victor Fteha is CC'd as the tech contact).

Enter the OnDeck API Key format

The API Key field takes exactly three values in this order, separated by commas with no spaces around the commas:

API key,username,password

Example:

123,[email protected],fBqRP*VEMm

  • Value 1: API key from OnDeck

  • Value 2: username

  • Value 3: password

Paste the full string from the credentials email OnDeck sent. Do not add spaces after commas, reverse the order, or leave out a value.

Connect the API in Development

Configure OnDeck on the funder page with Development credentials before you run a test deal.

  1. In MCA Pilot, go to Funders and create or open OnDeck.

  2. Open the Submission Method tab and click Edit.

  3. Choose API Integration as the Submission Method.

  4. Set API Funder to OnDeck.

  5. Set API Environment to Development.

  6. In API Key, paste your development credentials in the format above, then save.

Test the integration

Submit one complete test deal in Development and send the successful response to OnDeck before you ask for production access.

  1. Submit a test deal that includes all required fields and files listed below.

  2. On the deal page, hover over the submission and click Open in OnDeck to confirm it in your OnDeck portal.

  3. If the test succeeds, copy the Response and email it to Jack asking to move to production.

Switch to production

After OnDeck sends production credentials, replace the full key string and switch the environment before your first live submission.

  1. Wait for OnDeck to send production credentials. Do not reuse the development key string.

  2. Return to Funders → OnDeck → Submission Method → Edit.

  3. Replace the entire API Key value with the production string in the same format: API key,username,password (no spaces around commas).

  4. Change API Environment to Production.

  5. Save the Submission Method settings.

Production handoff checklist

Confirm every item below with your OnDeck contact before you submit the first production deal:

  • OnDeck approved your Development test and issued production credentials.

  • The full production credential string is in API Key (all three values replaced, not a partial edit of the old string).

  • API Environment is set to Production, not Development.

  • OnDeck confirmed the endpoint path no longer includes .staging.

  • You are using the production password OnDeck provided (OnDeck also changes the encrypted password for production).

Required fields

OnDeck submissions need these deal values filled in before you submit:

  • Business info, including EIN

  • Owner info, including phone

  • Revenue and balance: at least one Statement record in the Underwrite tab with Total revenue and Average daily balance filled out

  • App and banks (not required, but recommended)

Statement data comes from AI Underwriting. If you uploaded bank statements manually, open the Underwrite tab, click AI Underwriting, and wait until the status shows Complete. If statements arrived through your application form integration, AI Underwriting runs automatically.

Troubleshooting

Use these checks when credentials fail, production still routes like staging, or a submission errors.

Credentials are rejected or login fails

The API Key field must contain exactly three comma-separated values with no extra spaces: API key, username, and password, in that order. Copy the credentials directly from the email OnDeck sent and paste the full string into the field so you do not introduce typos or spaces.

Production handoff does not work

Switching to production is more than pasting a new key. Confirm all of the following, then save and resubmit:

  1. Replace the entire API Key string with production credentials in API key,username,password format.

  2. Set API Environment to Production.

  3. Verify with OnDeck that the endpoint path no longer includes .staging and that you are using the production password they provided.

Submission fails with missing fields

If any required value is blank, the submission errors. Fill in business info including EIN, owner info including phone, and at least one statement record in Underwrite with Total revenue and Average daily balance, then resubmit.

Submission still errors after fixing fields

Hover over the submission and click View error for the exact message. Common causes are an invalid phone number format, a missing App or Bank file, or a statement record that has not finished AI Underwriting. Wait until AI Underwriting shows Complete, then try again.

Negative average daily balance

MCA Pilot defaults a negative average daily balance to $0 for OnDeck submissions. To correct the value before submitting, open the Underwrite tab, open the statement record, and edit Average daily balance.

Support

If you have a question or run into issues, respond in the chat or call +1 888 501 1477.

Related Articles
Did this answer your question?