API Master
How each lender API operates and what emails fire on send.
Authentication required to view users
Elevate Funding
Merchant cash advance application, supporting documents, and automated processing through Elevate Partner API v1.
Elevate View username/password exchanged server-side for a two-hour JWT; user access verified before submission.
- ▸Business name, DBA, EIN, industry, phone, start date, entity type and business address
- ▸Primary owner and optional second owner: contact info, home address, SSN, date of birth and ownership percentage
- ▸Signed application PDF, up to 4 recent bank statement files, up to 3 processing statements, and available ID/check documents
- ▸Upload documents to the returned application ID, then request automated processing
Requires a signed application and at least three bank statement files covering three months. Confirm statement coverage before sending; processing statements are included when available. Requested amount is stored in customData because Elevate has no dedicated amount field. Partial submissions retain their Elevate ID for retries.
Checks sandbox sign-in and API access at api-dev.elevatefunding.com; does not send applications.
CFG Merchant Solutions
Synchronous merchant application + bank statements push (CFGMS App Submission API v1.4.0).
Basic HTTP Auth — API key as username, empty password
- ▸isoName, appPurpose, amountRequested (cents), avgMonthlyRevenue (cents)
- ▸business { name, address, ein, dba, industry, startDate, website }
- ▸owner1 + owner2 (if has_second_owner) — home address only, no mortgage fallback
- ▸applicationPdf (base64, watermarked, unredacted)
- ▸bankStatementPdfs (up to 4, base64, watermarked, unredacted)
grossAnnualRevenue removed. Owner home address read directly (no applicant_primary_residence fallback). All PDFs watermarked, contact info unredacted.
No FundingPartner record with api_partner_key="cfgms" exists yet. Create one on the Partners page to enable email controls.
Bitty Advance
Bitty Advance Portal Submission API V3 — instant pre-offer / decline / duplicate response.
API key in JSON body (apikey field, not a header)
- ▸apikey, development (bool), leadid, campaign, subid1
- ▸legal_name, dba_name, business address, ein, start_date, website
- ▸bank_name, bank_routing, bank_account
- ▸owners[] (up to 2 — address, phone, dob, ssn, fico, ownership %)
- ▸requested_amount, average_revenue, advance_current + up to 2 positions
- ▸files[] (type 1=App PDF, 2=Bank Statements x4, 3=DL, 4=Voided Check — base64, watermarked, unredacted)
Up to 4 bank statements attached. All PDFs watermarked, contact info unredacted.
Credibly
Credibly ISO API — builds SubmissionRequest (business_overview, account_overview, principals) from the application and POSTs to /v2/submissions.
JWT Bearer — fetched via /v2/get-jwt using X-API-KEY header (CREDIBLY_JWT_BEARER_UAT)
- ▸business_overview { legal_name, dba, business_address, city, state, zip, ownership_type, federal_tax_id (XX-XXXXXXX), start_date, website }
- ▸account_overview { avg_monthly_deposits }
- ▸principals[] { first_name, last_name, percent_ownership, ssn (XXX-XX-XXXX), address, city, state, zip, dob, email }
- ▸amount_requested (integer, optional — from product_requested_amounts.mca or requested_amount)
Builds the full Credibly SubmissionRequest from the application. EIN formatted XX-XXXXXXX, SSN formatted XXX-XX-XXXX, dates ISO-8601. Up to 2 principals. JWT auth via shared crediblyAuth module (X-API-KEY header).