> For the complete documentation index, see [llms.txt](https://help.clickatell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clickatell.com/developers-api-reference/developers-archive/bulk-sms-scripts/ruby-library.md).

# Ruby library

**Overview**

Use Clickatell’s Ruby scripts with our HTTP or REST messaging APIs to interact with the Clickatell SMS Gateway.

[Get Ruby library](https://github.com/clickatell/clickatell-ruby)

\
**When to use this**

Used mostly for websites and smaller programs. After signing up, use this Ruby code sample and start playing around.

\
**Installation and usage**

Required gems used in the examples that you will need to install:

| `gem install rest-client` |
| ------------------------- |

 

Documentation and extra functionality not used in the examples:

* [HTTP ](https://docs.clickatell.com/channels/sms-http-s-api-archived/using-the-http-api/)
* [REST ](https://docs.clickatell.com/channels/sms-api-documentation-archived/getting-started-with-our-apis/)

You can see our other libraries and more documentation at the [Clickatell APIs and Libraries Project](http://clickatell.github.io/).


---

# 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://help.clickatell.com/developers-api-reference/developers-archive/bulk-sms-scripts/ruby-library.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.