Requested links
Send a requested waiver, form or secure account link when your customer needs it.
Send the link. Confirm the order. Remind them of tomorrow. Connect your product to Message.com and keep every notification, delivery result and dollar in view.
Northline: Your order #1048 has shipped.
Track your delivery:
northline.example/track/1048
Reply STOP to opt out.
You see the delivery result.
For the messages customers requested—not an imported list of people to advertise to.
Send a requested waiver, form or secure account link when your customer needs it.
Keep customers informed when an order is confirmed, ready or on its way.
Send appointment and account reminders tied to events in your own system.
Waiver.com is preparing to connect Message.com so businesses can send requested waiver links and timely reminders from their existing workflow.
Integration in preparationThe business records permission to send waiver notifications.
Waiver.com requests a text through Message.com using its approved platform sender.
The integration checks completion and consent before sending another reminder.
Review sent, delivered, failed and unconfirmed messages in your SMS dashboard. Search by number and filter delivery results.
Follow your balance, SMS segments, usage deductions and registration payments. Set a monthly spending limit.
Sender approval, recorded consent, STOP suppression and per-recipient limits are checked before dispatch.
Use a dedicated API key, a stable request ID and status lookup. Keep credentials on your server and prevent duplicate sends.
Carrier acceptance is not confirmed delivery. The dashboard uses available delivery receipts; the notification API currently reports dispatch status, not delivery webhooks.
Prepaid delivery plus sender registration. No separate monthly notification software package. Review registration and number charges before payment.
One current notification API rate across supported US and Canadian destinations.
The notification API currently adds no separate carrier-fee debit. These rates apply to this API only. Promotional SMS, MMS and other messaging rates differ.
Start with prepaid creditsBusiness registration, campaign setup and the first three campaign months.
Credits, applicable number fees, optional vetting and taxes are separate. Payment submits the registration; carrier approval is a separate step.
This API uses an approved local number with an account- or delivery-notification campaign. Toll-free and Verify short-code senders are not supported by this endpoint.
A short GSM-7 text fits in 160 units; longer texts use 153 per segment. Unicode uses 70 units, or 67 per segment for longer texts. The registered business name and STOP footer count too. A two-segment notification costs 2¢.
Estimate your monthly delivery credits. One text can use more than one SMS segment.
Prepare your integration while your sender is reviewed.
Use the business operating the notification service. Add prepaid delivery credits.
Provide your company, use case, templates and consent flow. Pay registration fees and wait for approval.
Create a dedicated notification API key and follow the guide. Your integration details stay available in SMS settings.
Send to an authorized recipient. Check delivery, duplicate protection and STOP handling before customer traffic.
Authentication, request examples, consent fields, errors, limits and safe retries.
This API requires an approved local-number account-notification or delivery-notification campaign, even for non-marketing messages. Registration describes what you send and how recipients consent.
Describe the platform, tenant business names, message templates and consent flow in your registration. A shared sender must be approved for that actual program. Each tenant does not automatically receive permission to send arbitrary messages.
The notification API currently allows up to 1,000 dispatches per workspace and 10 per recipient in a rolling 24 hours. Campaign limits, credit balance, spending caps and opt-outs also apply. Your platform should enforce its own tenant quotas.
The API reserves 1¢ per segment before dispatch. Sends stopped before dispatch are refunded. An uncertain provider outcome keeps its reservation while it is reconciled; do not resend it as a new request.
Use the separate promotional SMS flow for marketing, or Message Verify for verification codes. This notification endpoint is for approved transactional use cases.
Connect your workflow. Keep control of your sending.