An SMS API for property management software needs to do three things well: send maintenance and rent texts reliably, respect each tenant's consent and opt-out, and keep every property manager customer separate, with its own number and carrier registration. Ready's API gives each customer a sub-account for that reason, so a platform can text for hundreds of managers without mixing their traffic.

Property software is a good fit for texting. Tenants read texts quickly, maintenance is full of short status updates, and rent is a recurring nudge. It's also a place where consent and timing mistakes are easy to make, because a single platform sends on behalf of many managers. This guide covers the message types, the consent question, and the account structure.

The messages tenants actually get

Most property software sends a handful of kinds of text:

  • Maintenance: request received, technician scheduled, on the way, work completed.
  • Rent: a reminder before the due date, a note when payment is received, a late notice.
  • Operations: showing confirmations, move-in instructions, lease renewal reminders.
  • Notices: planned water shutoffs, building access, emergencies.

Each of these is a transactional or conversational message between a manager and a tenant. Our payment reminder message post has wording ideas for the rent ones. Keep message bodies free of sensitive details like account balances in full or anything beyond what a tenant needs.

Consent comes from the tenant relationship, and you keep the proof

The sender attests consent. On Ready, an API send that sets consent_attested records that attestation: who sent, to how many, and when. It isn't a per-tenant consent record. Ready doesn't store each recipient's opt-in time, wording or page URL, so your software should keep that, often at lease signing or in the resident portal. The one exception is a sign-up on a Ready-hosted opt-in page, stored per contact; support@tryready.com can send a copy.

Practical advice:

  1. Collect text consent as its own checkbox in the lease packet or portal, with clear wording about the kind of messages.
  2. Store the date, wording and source in your own database.
  3. Pass consent_attested: true only for tenants who agreed.
  4. Treat an API send without it as a gap to close. It still goes out today, with a warning and no attestation.

Our consent record schema post shows a layout for storing this. Compliance is the sender's responsibility.

One sub-account per property manager

If your customers are property management companies, each one is a separate business. On Ready, each gets a sub-account with its own numbers and its own 10DLC registration. Create one with POST /v1/sub-accounts and list them with GET /v1/sub-accounts. Registration goes through POST /v1/registration/brand, POST /v1/registration/campaign and POST /v1/registration/confirm, with GET /v1/registration for status. See the sub-accounts docs and the registration docs.

The cost is itemized: $25 a month per customer for the brand and its first campaign, $20 a month for each extra campaign, $2 a month per number. Most approvals take 2 to 7 days. Ready registers businesses with an EIN only, so a very small landlord operating as a sole proprietor without an EIN can't register until they have one.

Per-manager separation also keeps opt-outs honest. A STOP always blocks that number in the sub-account that received it. For whether it also blocks other sub-accounts, check GET /v1/opt-outs/:phone.

Sending a maintenance update

curl -X POST https://api.tryready.com/v1/messages \
  -H "X-API-Key: $READY_API_KEY" \
  -H "Idempotency-Key: a41e7c90-5d2b-4b1f-8c63-7e09f2d3b5a8" \
  -H "Content-Type: application/json" \
  -d '{"to": "+12125550199", "body": "Maintenance update: your plumber is scheduled for Thursday between 9 and 11 AM.", "consent_attested": true}'

Use the sub-account's key so the text goes out from that manager's own number. Leave from out and Ready picks the number the tenant already texts with, otherwise the closest to their area code. The idempotency key matters here: a job queue that retries on a timeout will otherwise text a tenant twice about the same visit.

Rent reminders and quiet hours

Rent reminders are usually bulk. POST /v1/messages/bulk sends the same text to many numbers, up to 100 recipients per call, so split a large portfolio into batches. Send them only to tenants who agreed.

Timing rules apply. Quiet hours follow the recipient's area. Campaigns and automations wait up to 24 hours for the window. A single API text is held only if the window opens within 6 hours; otherwise the API answers 409 QUIET_HOURS_BLOCK and your software sends again once the window opens. A text in reply to a tenant who texted in the last 24 hours goes out at any hour, which helps with urgent maintenance conversations. For a scheduled reminder, POST /sms/schedule takes a send_at time for one contact.

Replies and the inbox

Tenants reply with things like "the leak is worse" and "can I pay Friday?" Those need a person. Replies land in the inbox, and your app can hear about them through webhooks; our inbound webhooks guide covers the pattern. For routing to the right manager or site team, see routing inbound texts to reps.

Don't put sensitive health or personal details in a text, and note that Ready isn't HIPAA compliant.

An example, with assumptions

Say a platform has 40 property manager customers, and each averages 600 tenants. Each manager sends one rent reminder a month that fits in one segment. That's 40 × 600 = 24,000 texts a month, or 24,000 segments, across 40 sub-accounts. Registration is 40 × $25 a month for brands and first campaigns, plus $2 a month for each number. The per-segment charge is the Standard rate plus the carrier fee, and screening is extra if switched on. These figures are assumptions for illustration, and your own counts will differ. See the pricing page for the current rates.

Quick checklist

AreaWhat to do
Account structureOne sub-account per property manager customer
RegistrationBrand and campaign per customer, EIN required
ConsentCapture at lease or portal, store it yourself, set consent_attested
Opt-outsHonor STOP, check GET /v1/opt-outs/:phone across systems
RetriesReuse the Idempotency-Key on every retry
TimingPlan for quiet hours on API sends

Frequently asked questions

Do rent reminders need consent?

Yes, treat them as texts that need the tenant's agreement, and store that agreement. Compliance is the sender's responsibility.

Can one number serve all my property manager customers?

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

What does it cost?

One Standard rate per segment plus the carrier fee, with screening extra if switched on. The pricing page has the figures. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

Next step

Map your customers to sub-accounts, decide where tenant consent will live, and run one test send from the API quickstart. The sub-account guide for vertical SaaS onboarding is a good second read.