curl --request GET \
--url https://api.1-funnel.org/v1/businesses/{businessId}/sms/messages/{messageId} \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.1-funnel.org/v1/businesses/{businessId}/sms/messages/{messageId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.1-funnel.org/v1/businesses/{businessId}/sms/messages/{messageId}"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)HttpResponse<String> response = Unirest.get("https://api.1-funnel.org/v1/businesses/{businessId}/sms/messages/{messageId}")
.header("Authorization", "Bearer <token>")
.asString();{
"id": "018f3c4e-7b2a-7c3d-8e9f-aaaaaaaaaaaa",
"business_id": "018f3c4e-7b2a-7c3d-8e9f-0123456789ab",
"from": "1FUNNEL",
"to": "+2348012345678",
"classification": "transactional",
"message": "Your order ORD-1001 is confirmed.",
"status": "delivered",
"status_reason": null,
"template": null,
"accepted_at": "2026-10-13T09:00:00.000Z",
"submitted_at": "2026-10-13T09:00:01.000Z",
"delivered_at": "2026-10-13T09:00:05.000Z",
"failed_at": null
}Retrieve an individual SMS
Business-scoped message detail (ADR-018 SMS-02). Cross-business existence is not disclosed (ADR-016).
curl --request GET \
--url https://api.1-funnel.org/v1/businesses/{businessId}/sms/messages/{messageId} \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.1-funnel.org/v1/businesses/{businessId}/sms/messages/{messageId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.1-funnel.org/v1/businesses/{businessId}/sms/messages/{messageId}"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)HttpResponse<String> response = Unirest.get("https://api.1-funnel.org/v1/businesses/{businessId}/sms/messages/{messageId}")
.header("Authorization", "Bearer <token>")
.asString();{
"id": "018f3c4e-7b2a-7c3d-8e9f-aaaaaaaaaaaa",
"business_id": "018f3c4e-7b2a-7c3d-8e9f-0123456789ab",
"from": "1FUNNEL",
"to": "+2348012345678",
"classification": "transactional",
"message": "Your order ORD-1001 is confirmed.",
"status": "delivered",
"status_reason": null,
"template": null,
"accepted_at": "2026-10-13T09:00:00.000Z",
"submitted_at": "2026-10-13T09:00:01.000Z",
"delivered_at": "2026-10-13T09:00:05.000Z",
"failed_at": null
}Authorizations
OAuth 2.0 Client Credentials for the External Integration API (ADR-015, ADR-023).
Client authentication: HTTP Basic (client_secret_basic).
Access-token audience: 1funnel-external-api.
The tokenUrl below is the production target. Sandbox uses a different
host. OpenAPI cannot bind tokenUrl to the selected servers entry; see
x-1funnel-oauth on the root document and the authentication guide when published.
Coarse OAuth scopes (if any) are token-level vocabulary (ADR-013 IA-06). They
are not the ADR-022 resource permission catalogue. Resource permissions
are enforced after token validation via application-to-business grants
(ADR-016) and are documented per operation with x-required-permissions.
These URLs are architecture targets. They are not claimed to be deployed or generally available.
Headers
Request correlation identifier (STD-API-01 D12). Clients may supply a value
of 1–128 characters matching A-Za-z0-9._-. Missing or invalid values are
replaced by a server-generated identifier. Distinct from W3C traceparent,
resource ids, Idempotency-Key, and webhook event ids.
1 - 128^[A-Za-z0-9._-]+$"req_01HZX3K9EXAMPLE"
Path Parameters
Business resource selector in /v1/businesses/{businessId}/… (ADR-006).
UUIDv7-compatible opaque identifier. {businessId} is not authorization
proof. The resource server must independently verify an active
application-to-business grant, required permission, and ownership (ADR-016,
ADR-022).
UUID with version nibble 7 (UUIDv7). STD-API-01 prefers UUIDv7 for new
platform-generated external resource identifiers. Clients must still treat
the value as opaque. Not every path parameter is guaranteed to be v7 solely
because it is a UUID; use this schema where the contract asserts UUIDv7.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-7[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$"018f3c4e-7b2a-7c3d-8e9f-0123456789ab"
Individual SMS message identifier (UUIDv7). Not authorization proof.
UUID with version nibble 7 (UUIDv7). STD-API-01 prefers UUIDv7 for new
platform-generated external resource identifiers. Clients must still treat
the value as opaque. Not every path parameter is guaranteed to be v7 solely
because it is a UUID; use this schema where the contract asserts UUIDv7.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-7[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$"018f3c4e-7b2a-7c3d-8e9f-0123456789ab"
Response
Message detail
Individual SMS resource. Acceptance is not delivery confirmation. Status is the merchant-visible display projection (ADR-018 SMS-12).
UUID with version nibble 7 (UUIDv7). STD-API-01 prefers UUIDv7 for new
platform-generated external resource identifiers. Clients must still treat
the value as opaque. Not every path parameter is guaranteed to be v7 solely
because it is a UUID; use this schema where the contract asserts UUIDv7.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-7[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$"018f3c4e-7b2a-7c3d-8e9f-0123456789ab"
UUID with version nibble 7 (UUIDv7). STD-API-01 prefers UUIDv7 for new
platform-generated external resource identifiers. Clients must still treat
the value as opaque. Not every path parameter is guaranteed to be v7 solely
because it is a UUID; use this schema where the contract asserts UUIDv7.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-7[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$"018f3c4e-7b2a-7c3d-8e9f-0123456789ab"
Authorized sender identity for the business (from). The backend validates
that the application/business may use this sender. Arbitrary sender IDs are
not permitted. Public sender-ID management resources remain future
(ADR-018 SMS-19 / target architecture).
1 - 20"1FUNNEL"
Recipient MSISDN in E.164 format (+ followed by country code and subscriber
number). Leading + required.
9 - 16^\+[1-9]\d{7,14}$"+2348012345678"
Public message classification (lowercase snake_case). Transactional vs promotional distinction for compliance and routing policy.
transactional, promotional "transactional"
Merchant-visible individual message status (ADR-018 SMS-12). Display projection — not bulk processing status and not raw provider codes.
queued, sent, delivered, failed "delivered"
Durable acceptance timestamp (not provider submission or delivery).
"2026-10-13T09:00:00.000Z"
Effective message content after any template rendering at acceptance.
Optional finer failure or state detail. Not a provider-native code.
Revision pinned at durable acceptance when template-based.
Show child attributes
Show child attributes
{
"template_id": "018f3c4e-7b2a-7c3d-8e9f-0123456789ab",
"revision_id": "018f3c4e-7b2a-7c3d-8e9f-0123456789cd"
}
Provider submission timestamp when known.
"2026-10-13T09:00:00.000Z"
Delivery outcome timestamp when known.
"2026-10-13T09:00:00.000Z"
RFC 3339 date-time. Response timestamps are UTC with a Z offset
(STD-API-01 D06). Client-supplied timestamps must include an explicit offset;
local times without an offset are rejected.
"2026-10-13T09:00:00.000Z"