> For the complete documentation index, see [llms.txt](https://vezeti-dyno.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vezeti-dyno.gitbook.io/docs/vezetidyno-developer-api.md).

# VezetiDyno Developer API

Welcome to the VezetiDyno API Documentation! This comprehensive guide helps you integrate multi-channel messaging capabilities into your applications.

VezetiDyno enables you to send messages across multiple channels including Email, SMS, MMS, Voice, and Omnichannel campaigns with a unified API interface.

**Getting Started**

The VezetiDyno API uses REST principles with JSON request/response bodies. Authentication is handled via API keys passed in the `X-API-Key` header.

**Production**

**Base URL**

[`https://vezeti-be-wbzlc.ondigitalocean.app`](https://vezeti-be-wbzlc.ondigitalocean.app/)

## Getting Started

1. **Create an account**\
   Sign up for a VezetiDyno account at [cloudivi.com](https://cloudivi.com/).
2. **Generate your API key**\
   Navigate to Settings > API Keys in your VezetiDyno dashboard to generate your authentication key.
3. **Send your first message**\
   Call the POST `/api/messages` endpoint with your API key to send your first message.

## Features

* **Multi-Channel Messaging**\
  Send messages via Email, SMS, MMS, Voice, and Omnichannel
* **Scheduling**\
  Schedule messages for one-time, daily, weekly, or custom delivery
* **Contact Management**\
  Organise recipients into groups and manage contact lists

{% hint style="warning" %}
Always keep your API keys secure and never expose them in client-side code.
{% endhint %}


---

# 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://vezeti-dyno.gitbook.io/docs/vezetidyno-developer-api.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.