Bright Pattern SMS/MMS Messaging API
These methods enable sending of SMS and MMS messages and checking the delivery status. The response parameters are explained below.Response parametersParameterDescriptiontenant_idUnique identifier of your contact center in BPCC configuraiton.api_versionAPI version.bodyText of the message.num_segmentsNumber of segments in the transmitted message. Messages exceeding 160 characters are transmitted in multiple segements. In the current verison of API this parameters is always set to 1.num_mediaNumber of media files in the MMS message.date_createdTimestamp of the original Send Message request.date_sentTimestamp of message transmission. Set to "null" in responses to Send Message requests. Set to actual time when the message was sent in responses to Get Message requests.date_updatedReserved.directionAlways set to outboound-api.error_codeError code.error_messageError message.fromOrigin number or, if a messenger integration is being used, the messenger type and integration ID.priceReserved. In the current version of the API always set to null.sidUnique identifier of the message. Retured in response to a Send Message request and can be used in Get Message to check the delivery status of the message.statusStatus of message delivery. Possible values: queued (message queued to be sent), sent (message sent to SMS/MMS service provider but delivery not confirmed), delivered (message confirmed by SMS service provider to be delivered; currently not available for MMS), failed (message could not be sent; typically more details will be provided in error_message). Note that a 200 OK response to a Send Message request will always have status set to queued. Actual status of message delivery can be verified using the Get Message method with a slight delay.toDestination number or, if a messenger integration is being used, the messenger type and the messenger ID of the recipient.uriReserved.
Bright Pattern SMS/MMS Messaging API is one of 14 APIs that Bright Pattern publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include SMS/MMS Messaging. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 2 operations across 2 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against a single base URL, https://{tenant_url}.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Bright Pattern SMS/MMS Messaging API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
It supports OAuth 2.0 (oauth2ClientCredentials) using the clientCredentials flow.
By default, every request must be authenticated.
bearerAuth— OAuth 2.0 access token issued by the Bright Pattern token endpoint, sent as Authorization: Bearer .oauth2ClientCredentials— OAuth 2.0 client-credentials grant against the Bright Pattern tenant token endpoint.
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
These methods enable sending of SMS and MMS messages and checking the delivery status. The response parameters are explained below. Response parameters Parameter Description tenan…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Bright Pattern 12
Other APIs Bright Pattern publishes across the network.
This is an independent, third-party profile of Bright Pattern SMS/MMS Messaging API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.