---
title: "Send sms messages using query parameters."
method: POST
path: "/v4/sms/outgoing/sendusingquery"
tags: ["Sms - Outgoing"]
---

# Send sms messages using query parameters.

`POST /v4/sms/outgoing/sendusingquery`

## Request

- Base URL: `https://api.inmobile.com`
- URL: `https://api.inmobile.com/v4/sms/outgoing/sendusingquery`
- Auth: one of:
  - HTTP basic
  - API key in query parameter `apikey`

It is strongly recommended to use the POST version instead of this version to send text messages. This endpoint is only a emergency fallback option for systems that are not capable of doing an HTTP post.

## Query parameters

- `Text` string
- `From` string
- `Flash` boolean, nullable
- `Encoding` string
- `To` string
- `CountryHint` string
- `MessageId` string
- `RespectBlacklist` boolean, nullable
- `ValidityPeriodInSeconds` integer, nullable
- `StatusCallbackUrl` string
- `SendTime.UtcTime` string, date-time
- `SendTime.LocalServerTime` string, date-time
- `MsisdnCooldownInMinutes` integer, nullable

## Response `200`

- SmsOutgoingPostReply
  - `results` SmsOutgoingApiCreateResultModel[]
    - `numberDetails` NumberDetails
      - `countryCode` string: The country code part of the msisdn, e.g. 45.
      - `phoneNumber` string: The phone number part of the msisdn, e.g. 12345678.
      - `rawMsisdn` string: The input msisdn in its unaltered format. This is the value provided when sending the text message.
      - `msisdn` string: The final cleaned msisdn.
      - `isValidMsisdn` boolean: True if the input msisdn was valid.
      - `countryHint` string: The country code hint if provided in the request.
    - `text` string: The text message.
    - `from` string: The sender.
    - `smsCount` integer: The number of sms messages this message will be split into when sent to the operator. Charging will also be done according to this number.
    - `messageId` string: An optional message id used to identify the message. If no message id is provided, a new message id is generated and assigned to the message. This id must be unique across all messages created on the same account. (In case a previous message has been deleted according to GDPR deletion rules setup on the specific account, the messageId is allowed to be reused)
    - `encoding` string: The encoding of the message. Can be either "gsm7" or "ucs2". In case the message was submitted with encoding "auto", this report will reveal the final encoding based on the characters in the message text. "gsm7" is the default alphabet for text messages and when using gsm7, a single sms message can contain 160 characters. If the length exceeds 160 characters, the message is actually split up into parts of 153 characters and charged according to this. Please note, that a few, specific characters fill up 2 bytes and count for 2 letters. Ref: https://en.wikipedia.org/wiki/GSM_03.38 "ucs2" allows for more non-roman characters to be used along with smileys. When using this encoding, a single message can consist of 70 characters. If the message exceeds 70 characters, the final message is actually split into parts of 67 characters.

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `409`: Conflict
- `500`: Internal server error

---

[API](https://skmtc.dev/inmobile/apis/inmobile-rest-api.md) · [All operations](https://skmtc.dev/inmobile/apis/inmobile-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/inmobile/apis/inmobile-rest-api/revisions/197a90ad5f8f?raw)
