> ## Documentation Index > Fetch the complete documentation index at: https://www.vobiz.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Retrieve a message > Returns one message with its full status history. Use it to follow a message from `sent` to `delivered` or `failed`, and to read `errorCode` and `errorMessage` when it fails. ## OpenAPI ````yaml openapi-sms.yaml GET /messages/{id} openapi: 3.0.3 info: title: Vobiz Messaging API description: > Send and receive SMS, MMS and RCS messages, buy messaging numbers, register for US 10DLC and toll-free, run broadcasts, manage conversations, opt-outs and webhooks. **Base URL:** `https://api.vobiz.ai/api/v1/sms` **Authentication:** every request needs the `X-Auth-ID` and `X-Auth-Token` headers. The account is taken from your credentials; you never put an account ID in a path or body. Field names in this API are camelCase. version: '1.0' contact: email: support@vobiz.ai url: https://vobiz.ai servers: - url: https://api.vobiz.ai/api/v1/sms description: Production security: - AuthID: [] AuthToken: [] tags: - name: Messages description: Send messages and inspect their delivery state. - name: Numbers description: >- Messaging-capable numbers on your account, inventory search, purchase and release. - name: Coverage description: Where you can send, per country. - name: Conversations description: Two-way threads between one of your numbers and a contact. - name: Opt-outs description: Numbers that must not receive messages on a channel. - name: Webhooks description: Subscriptions that deliver message and broadcast events to your server. - name: Broadcasts description: Bulk sends from an uploaded recipient list. - name: RCS Senders description: RCS sender (agent) identities and their message templates. - name: 10DLC Brands description: US 10DLC brand registration. - name: 10DLC Campaigns description: US 10DLC campaigns, toll-free verification and supporting documents. paths: /messages/{id}: get: tags: - Messages summary: Retrieve a message description: >- Returns one message with its full status history. Use it to follow a message from `sent` to `delivered` or `failed`, and to read `errorCode` and `errorMessage` when it fails. The `statusHistory` array lists every status change, oldest first. For real-time updates, subscribe to webhooks (callbacks) or the WebSocket instead of polling. operationId: get-message parameters: - name: id in: path required: true schema: type: string format: uuid example: 9b2e1c40-8a3d-4f5e-9c1a-7d6b2e8f4a01 description: >- The message `id` (UUID) returned by `POST /messages`, `GET /messages`, a conversation, or an event. responses: '200': description: The message and its status history. content: application/json: schema: $ref: '#/components/schemas/MessageWithHistory' example: id: 9b2e1c40-8a3d-4f5e-9c1a-7d6b2e8f4a01 accountId: MA_XXXXXXXX direction: out channel: sms from: '+14155550100' to: '+14155550123' text: Your verification code is 482913 mediaUrls: [] status: delivered conversationId: c7d1e9a3-2b4f-4a6c-8d5e-1f3a9b7c2e04 createdAt: '2026-10-12T10:30:00Z' updatedAt: '2026-10-12T10:31:04Z' statusHistory: - status: sent createdAt: '2026-10-12T10:30:00Z' - status: delivered createdAt: '2026-10-12T10:31:04Z' '401': $ref: '#/components/responses/Unauthorized' '404': description: The message does not exist on your account. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message not found x-codeSamples: - lang: typescript label: Node SDK source: > import { VobizClient } from "@vobiz/sdk"; const client = new VobizClient({ apiKey: "MA_XXXXXXXX", authToken: "YOUR_AUTH_TOKEN" }); await client.sms.messages.getMessage({ id: "9b2e1c40-8a3d-4f5e-9c1a-7d6b2e8f4a01" }) - lang: python label: Python SDK source: | from vobiz import Vobiz client = Vobiz(api_key="MA_XXXXXXXX", auth_token="YOUR_AUTH_TOKEN") client.sms.messages.get_message( id="9b2e1c40-8a3d-4f5e-9c1a-7d6b2e8f4a01", ) - lang: go label: Go SDK source: | import ( "context" vobiz "github.com/vobiz-ai/Vobiz-Go-SDK" "github.com/vobiz-ai/Vobiz-Go-SDK/client" "github.com/vobiz-ai/Vobiz-Go-SDK/option" "github.com/vobiz-ai/Vobiz-Go-SDK/sms" ) c := client.NewClient( option.WithAPIKey("MA_XXXXXXXX"), option.WithAuthToken("YOUR_AUTH_TOKEN"), ) request := &sms.GetMessageRequest{ ID: "9b2e1c40-8a3d-4f5e-9c1a-7d6b2e8f4a01", } c.Sms.Messages.GetMessage( context.TODO(), request, ) - lang: java label: Java SDK source: | import com.vobiz.api.VobizApiClient; VobizApiClient client = VobizApiClient .builder() .apiKey("MA_XXXXXXXX") .authToken("YOUR_AUTH_TOKEN") .build(); client.sms().messages().getMessage( "9b2e1c40-8a3d-4f5e-9c1a-7d6b2e8f4a01", GetMessageRequest .builder() .build() ); - lang: ruby label: Ruby SDK source: > require 'vobiz' client = Vobiz::Client.new(api_key: 'MA_XXXXXXXX', auth_token: 'YOUR_AUTH_TOKEN') client.sms.messages.get_message(id: "9b2e1c40-8a3d-4f5e-9c1a-7d6b2e8f4a01") - lang: csharp label: C# SDK source: | using Vobiz; using Vobiz.Sms; var client = new VobizApiClient("YOUR_AUTH_TOKEN", "MA_XXXXXXXX"); await client.Sms.Messages.GetMessageAsync( new GetMessageRequest { Id = "9b2e1c40-8a3d-4f5e-9c1a-7d6b2e8f4a01" } ); - lang: php label: PHP SDK source: > sms->messages->getMessage( '9b2e1c40-8a3d-4f5e-9c1a-7d6b2e8f4a01', ); components: schemas: MessageWithHistory: allOf: - $ref: '#/components/schemas/Message' - type: object properties: statusHistory: type: array nullable: true description: >- Every status the message has passed through, oldest first, each with its time and any error detail. `null` when no status change has been recorded. items: $ref: '#/components/schemas/MessageStatusEntry' description: >- A message with its full status history, as returned by `GET /messages/{id}`. It has every field of the message object plus `statusHistory`. Error: type: object description: >- The body of every error response: a flat object with one `error` string that explains what went wrong. Use the HTTP status code to decide how to handle the error, and log `error` for diagnosis. required: - error properties: error: type: string example: 'recipient has opted out: +14155550123' description: >- Human-readable explanation of the error, for example `phoneNumber is required` or `recipient has opted out: +14155550123`. Branch on the HTTP status code rather than on this text. Message: type: object description: >- One message sent from or received by your account. Each recipient of a send gets its own message object with its own `id`, status and conversation. properties: id: type: string format: uuid example: 9b2e1c40-8a3d-4f5e-9c1a-7d6b2e8f4a01 description: >- Unique identifier of the message (UUID). Use it with `GET /messages/{id}` and to match status events. accountId: type: string description: Your Vobiz account ID (Auth ID), for example `MA_XXXXXXXX`. example: MA_XXXXXXXX direction: type: string enum: - out - in description: >- `out` for a message you sent, `in` for a message one of your numbers received. channel: type: string enum: - sms - mms - rcs description: >- Channel the message actually used: `sms`, `mms` or `rcs`. It can differ from the one you requested, for example `mms` after an SMS with media to US or Canadian numbers, or `sms` after an RCS send fell back with `failoverToSms`. from: type: string example: '+14155550100' description: >- Sender. For outbound messages, your number in E.164 format or the `senderName` of your RCS sender; for inbound messages, the contact's number. to: type: string example: '+14155550123' description: >- Recipient. For outbound messages, the contact's number in E.164 format; for inbound messages, your number. text: type: string example: Your verification code is 482913 description: >- Message body. An empty string when the message has no text, for example an MMS with media only. mediaUrls: type: array nullable: true items: type: string format: uri description: >- HTTPS URLs of the media attached to the message. `null` or an empty array when there is no media. status: type: string enum: - scheduled - sent - delivered - failed - received - unknown description: >- Where the message is in its lifecycle: `scheduled` (held for `scheduledAt`), `sent` (handed to the network), `delivered` (delivery confirmed), `failed` (see `errorCode` and `errorMessage`), `received` (inbound) or `unknown` (the network reported a status that maps to none of the others). errorCode: type: string description: >- Error code reported for a failed message. Omitted when there is no error. errorMessage: type: string description: >- Human-readable reason a message failed. Omitted when there is no error; quote it to support when you need help with a failure. tag: type: string description: >- The label you set when sending, for filtering and reporting. Omitted when none was set. conversationId: type: string format: uuid description: >- UUID of the conversation the message belongs to. Use it with `GET /conversations/{id}/messages` to load the thread. scheduledAt: type: string format: date-time description: >- The time you asked the message to be held until (ISO 8601, UTC). Omitted for messages that were not scheduled. createdAt: type: string format: date-time example: '2026-10-12T10:30:00Z' description: >- When the message was created, as an RFC 3339 / ISO 8601 timestamp in UTC. updatedAt: type: string format: date-time example: '2026-10-12T10:30:00Z' description: >- When the message last changed, for example on a status update (ISO 8601, UTC). MessageStatusEntry: type: object properties: status: type: string enum: - scheduled - sent - delivered - failed - received - unknown description: >- The status the message moved to: `scheduled`, `sent`, `delivered`, `failed`, `received` or `unknown`. errorCode: type: string description: >- Error code reported with this status. Omitted unless the entry records a failure. errorMessage: type: string description: >- Human-readable failure reason reported with this status. Omitted unless the entry records a failure. provider: type: string description: Internal routing identifier; do not rely on its value. createdAt: type: string format: date-time description: When the message reached this status (ISO 8601, UTC). description: >- One entry in a message's status history: a status the message reached and when. responses: Unauthorized: description: Missing or invalid `X-Auth-ID` / `X-Auth-Token`. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: missing or invalid credentials securitySchemes: AuthID: type: apiKey in: header name: X-Auth-ID description: Your Vobiz account Auth ID (`MA_XXXXXXXX`). AuthToken: type: apiKey in: header name: X-Auth-Token description: Your Vobiz account Auth Token. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.