An SMS API for mortgage and loan software has to do three jobs. It sends short status texts at the right moment, it respects each borrower's consent and STOP, and it keeps every lender or broker on your platform separate, with its own number and carrier registration. Ready's API covers the sending, the opt-out handling and the per-customer separation. The consent record and the message content stay yours.

Loan work is full of waiting. A borrower uploads pay stubs, then wonders for two days whether anyone saw them. A text that says "we got your documents" is cheap and useful. It's also a place where timing and wording mistakes are easy to make, because one platform texts on behalf of many lenders. We make Ready, and every example below is a made-up example with stated assumptions.

Which texts a loan platform actually sends

Most origination and servicing-adjacent software sends the same few kinds of message:

  • Document requests: "We still need your most recent pay stub. Upload it in your portal."
  • Milestone updates: application received, in underwriting, conditions cleared, closing scheduled.
  • Appointment reminders: a closing, a signing or a call with the loan officer.
  • Replies: a borrower answers "which bank statement?" and a person needs to see it.

Each one is a message between a lender and a borrower who agreed to hear from them. Keep the body short and free of sensitive detail. A link to the portal is better than a loan balance, an income figure or a full account number in the text itself.

Consent: collected by you, attested on each send

On Ready, an API send that sets consent_attested records your statement that the recipient agreed to texts: who sent, to how many, and when. It isn't a per-borrower consent record. Ready doesn't store each person's opt-in time, wording or source, so your software has to.

A workable setup for a loan platform:

  1. Add a separate text-consent checkbox to the application or the portal sign-up, with plain wording about the kinds of messages.
  2. Store the date, the exact wording and the source in your own database.
  3. Pass consent_attested: true only for borrowers who ticked it.
  4. Never text a purchased or scraped list, and don't treat a lead's web form as consent to text unless the form said so.

Our consent record schema for developers shows a layout for storing this. Compliance is the sender's responsibility, and lending is a regulated field, so have your own counsel review the wording.

One sub-account per lender

If your customers are separate lenders, brokers or credit unions, each one is its own business. On Ready each gets a sub-account with its own numbers and its own 10DLC registration, created through the API. That keeps one lender's complaints and opt-outs from dragging down another's sending.

ItemWhat it looks like per lender
Sub-accountOne per lender or broker
RegistrationBrand and campaign filed per customer, EIN required
Brand and first campaign$25 a month
Number$2 a month each
Typical approvalMost approvals take 2 to 7 days

Ready registers businesses with an EIN only. A loan officer working as a sole proprietor gets an EIN first. The sub-account onboarding guide for vertical SaaS walks through the order of operations, and know-your-customer checks for sub-accounts covers who you let onto the platform.

Sending a milestone text

One request sends one text. Use the lender's sub-account key so it goes out from that lender's own number:

curl -X POST https://api.tryready.com/v1/messages \
  -H "X-API-Key: $READY_API_KEY" \
  -H "Idempotency-Key: 6c1f0a52-91d4-4e0b-a7d3-2b8e5f40c913" \
  -H "Content-Type: application/json" \
  -d '{"to": "+12125550142", "body": "Example Lending: your documents were received. Log in to your portal to see what is left.", "consent_attested": true}'

Leave from out and Ready picks the number the borrower already texts with, otherwise your primary number. Build the idempotency key from your own event ID, such as the milestone row. A job queue that retries after a timeout would otherwise text the same borrower twice. Full request details are in the messages API docs.

Quiet hours and STOP

Quiet hours follow the recipient's area, not yours. A processor working late shouldn't mean a borrower gets a text at midnight. Here's how Ready treats each path:

  • Campaigns, drip campaigns and automations wait up to 24 hours for the window to open.
  • A single API text is held only if the window opens within 6 hours. Otherwise the API answers 409 QUIET_HOURS_BLOCK, nothing is sent, and your software sends it again once the window opens.

So a "conditions cleared" event at 11 PM local time shouldn't be treated as lost. Catch the 409 and requeue it for morning. Our quiet hours 409 guide has the pattern.

STOP is handled for you. When a borrower replies STOP, Ready honors it and blocks further texts to that number, and a refused send isn't charged. A STOP always blocks that number in the sub-account that received it. To see whether it reaches other sub-accounts, call GET /v1/opt-outs/:phone. If you also email or call, our opt-out API guide explains how to mirror a STOP into your own records.

What not to put in a text

Keep it to status and a pointer. Don't send a Social Security number, a full account number, an income figure or a loan balance. Ready isn't HIPAA compliant and doesn't sign BAAs, and a text is not a secure channel for anything you wouldn't want read on a lock screen. "Your closing is Friday at 2 PM, see your portal for details" does the job.

Two more limits matter for a lender. Ready's acceptable-use policy bars debt collection texting and bought lists, so this guide is about borrowers who applied and agreed, not outreach to strangers. Marketing-style texts also carry more consent weight than a status update, so keep the two kinds apart in your data.

An example, with assumptions

Say a platform has 30 lender customers, and each sends 400 one-segment milestone texts a month. That's 30 x 400 = 12,000 texts, or 12,000 segments. At $0.0075 per segment plus a $0.0045 carrier fee, the sending cost is 12,000 x ($0.0075 + $0.0045). Add registration for 30 sub-accounts and a number each. Replies are billed like sent texts, so if borrowers answer one text in five, count 2,400 more segments. These are example assumptions, not a forecast. The pricing page has the current figures.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

Next step

Decide where borrower consent will live, map each lender to a sub-account, and run one test send from the API. If you've built something similar for tenants, SMS API for property management software has the same shape with different message types. Start with the API quickstart and a single lender.

Frequently asked questions

Do status texts to a borrower need consent?

Treat them as texts that need the borrower's agreement, and store that agreement yourself. Compliance is the sender's responsibility.

Can one number serve every lender on my platform?

It's better not to. Each lender should have its own sub-account, number and registration so their traffic and reputation stay separate.

Can I text borrowers about overdue payments?

Don't use Ready for debt collection texts. Its acceptable-use policy bars the category.