SMS Notifications
Send an SMS notification
Sends an SMS message to a clinic client on behalf of a clinic.
Important limitations:
- Message length: Individual carriers impose their own limits on message length, and these limits can change over time. Messages that exceed a carrier’s limit may be split, truncated, or outright rejected.
- Rate limits: SMS sending is subject to overall, per-carrier, and daily rate limits. These limits are shared across all messages sent from your clinics — including messages sent by Vetcove on your behalf through other features in our platform. This endpoint enforces a limit of 20 requests per second and 200,000 requests per day per organization. These limits are not per carrier, so if your messages are not well distributed across carriers it is possible to stay within our limits while still exceeding the per-carrier limits of our third-party SMS provider.
- Trust score: Your organization is assigned a trust score by the underlying SMS provider. The content and volume of messages you send directly affects this score. Sending spammy, inappropriate, or excessive messages can lower your score, resulting in stricter rate limits and reduced deliverability across all of your clinic communications.
POST
Send an SMS notification
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
Response
Created
The SMS message body.
The ID of the client communication number the SMS was sent to.
The ID of the clinic client the SMS was sent to.
The ID of the clinic the SMS was sent from.
When the SMS notification was created.
Error code from the SMS provider if sending failed.
Human-readable reason for the error, if the error code is recognized.
The ID of the SMS notification.
The delivery status of the SMS.
SENT: Message was sent but delivery is not yet confirmed.DELIVERED: Message was successfully delivered.FAILED_TO_SEND: Message failed to send.
Available options:
SENT, DELIVERED, FAILED_TO_SEND