This is the article to send a skeptical engineer. Loanable is a U.S. business funding marketplace, not a lender. Embedded solutions mean you can send your users into a Loanable-branded or co-branded application with partner attribution. The live path is your unique partner link, optionally with a product type. When a lender in the 150+ network funds, you earn 50/50 of Loanable profit, paid Monday via ACH, with no minimum.
Loanable does not offer a public REST lending API that returns offers, books loans, or moves money into your customer’s account on a token. If a salesperson implied that, this paragraph is the correction. Private operational tools may exist for Loanable’s own team. They are not a developer platform you should spec against in Jira.
What you do get
A unique code. An apply experience you can brand or co-brand. A partner dashboard for attributed applications and fundings. Weekly ACH. Coverage across working capital, term, SBA, equipment, and lines of credit, with large facilities able to reach $50M when appropriate. Timing that can be as soon as 24 hours on some working-capital files. Support that understands you are a software or payments company, not an ISO desk, if you tell them that during onboarding.
- You get attribution, not a credit policy you own
- You get a marketplace, not a warehouse line
- You get partner payouts, not borrower disbursements through your software
- You get HTML and URLs, not an undocumented /v1/underwrite
What you must still do
Place the button. Preserve the ref. Write honest copy. Train support. Do not auto-file applications. Do not scrape bank logins into a spreadsheet. Do not tell users you funded them. Those are still your product obligations.
If you need a true API
Build with a licensed lender or bank partner who actually provides one, or become that program with counsel. Do not wait for Loanable’s marketplace apply flow to grow a public credit API because a blog post wished it. Use the apply flow for the coverage you can offer this quarter.
A one-slide internal summary
Marketplace, not lender. Apply flow, not public REST API. Ref code attribution. 150+ lenders. 50/50 of Loanable profit. Monday ACH, no minimum. Working capital as soon as 24 hours in some cases. Products can reach $50M when the file and a lender support it. Branded or co-branded UI. Partner dashboard. That is the offer. If a bullet is not on this slide, do not put it in a customer-facing roadmap.
Pin the slide in the partnership channel. When a PM adds “in-app instant decision,” point at the slide. When a seller adds “our API,” point at the slide. Embedded solutions stay shippable when the company repeats the same boundary. unique partner link is the integration surface. Everything else is a different company.
If a customer RFP asks for “lending API documentation,” attach a one-pager that says the integration is an attributed apply flow, lists a unique partner link, and states there is no public REST underwriting API. You will lose some RFPs. You will also stop winning work you cannot deliver. 150+ lenders, 50/50 Monday ACH, as-soon-as-24-hour working capital, and facilities up to $50M are true of the marketplace. They are not true of a swagger file you do not have.
Spec the partnership that exists. Read Loanable embedded solutions as an apply-flow product with partner-link attribution, not as a REST lending platform.