> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/flows/sms-flows.md).

# SMS Flows

This part of the document contains the list of services that can be integrated in flows above. 2 configuration parameters will be shared during integration:

| username | Username for basic authentication |
| -------- | --------------------------------- |
| password | Password for basic authentication |

### send-sms (POST)

This service is used to send a SMS. Use '/n' escape char to add new line.

**URL**

```
^^/send-sms/
```

**Request Headers**

| Header               | Description                                  |
| -------------------- | -------------------------------------------- |
| x-akinon-request-id  | Unique ID for problem solving & tracing.     |
| x-akinon-api-version | Akinon Customer API version.                 |
| Authorization        | “Basic {BASE64\_encoded(username:password)}” |

**Request Body raw (json)**

```json
{
  "from": "", //e.g. AKINON
  "to": "", //in E-164 format, e.g. +905323001020
  "text": "",
  "isOtp": false //OPTIONAL, default: false
}
```

**Response 201 (with no body)**

### Response Body For Errors (ALL)

If any errors are encountered in the services, these errors should be reported in the format below, and the list of error codes should be shared with Akinon.

**Response Body raw 4xx/5xx (json)**

```json
{
    "errors": [
       {
           "code": "",
           "field": "",
           "message": ""
       }
   ]
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://apidocs.akinon.com/flows/sms-flows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.