> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linkiasoft.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Send and read messages across WhatsApp, Instagram, Messenger and Telegram from your own systems.

The Linkiasoft API lets your own systems work with customer conversations and the CRM behind
them — notify a customer when their ticket closes, pull a thread into your helpdesk, move a
lead through your pipeline, or log a follow-up from a workflow you already run.

**Two hosts, one key.** Messaging and CRM are separate services, and every endpoint page
shows which one it uses. The same API key authenticates against both.

|                                                | Base URL                            |
| ---------------------------------------------- | ----------------------------------- |
| Messaging — conversations, templates, channels | `https://social.linkiasoft.com/api` |
| CRM — leads, stages, contacts, activities      | `https://api.linkiasoft.com/api`    |

## What you can do

<CardGroup cols={2}>
  <Card title="Send a message" icon="paper-plane" href="/api-reference/conversations/send-a-message">
    Templates, media, or plain text — one endpoint for all three.
  </Card>

  <Card title="Read conversations" icon="comments" href="/api-reference/conversations/list-conversations">
    List threads and page through their message history.
  </Card>

  <Card title="List templates" icon="table-list" href="/api-reference/templates/list-approved-templates-for-a-channel">
    See which approved WhatsApp templates a channel can send.
  </Card>

  <Card title="Find your channels" icon="plug" href="/api-reference/channels/list-your-connected-channels">
    Every other endpoint needs a `channelId` — this is where you get it.
  </Card>

  <Card title="Move a lead" icon="chart-line" href="/leads">
    Read your pipeline stages, change a lead's stage, reassign it.
  </Card>

  <Card title="Log a follow-up" icon="phone" href="/leads#mark-a-follow-up">
    Record a call, email or meeting against a lead.
  </Card>

  <Card title="Contacts at a company" icon="address-book" href="/api-reference/contacts/list-contacts-for-a-company">
    The people attached to a customer record.
  </Card>
</CardGroup>

## Before your first call

<Steps>
  <Step title="Create an API key">
    In Linkiasoft, go to **Settings → API Keys**. The key is shown once, at creation — copy it
    then. Give it only the scopes the integration needs; see [Authentication](/authentication).
  </Step>

  <Step title="Find your channel">
    Call [`GET /v1/connect/channels`](/api-reference/channels/list-your-connected-channels). The `id` of the
    channel you want to send from is the `channelId` every other endpoint asks for.
  </Step>

  <Step title="Send something">
    Follow the [quickstart](/quickstart) to send your first template.
  </Step>
</Steps>

## The one WhatsApp rule that catches everyone

WhatsApp only lets you send free-form text within **24 hours of the customer's last
message**. Outside that window — which is almost always the case for a notification your
system initiates — you must send an **approved template**.

<Warning>
  A plain-text send to a customer who hasn't messaged you recently will be rejected by
  WhatsApp, not by us. If your integration sends notifications, it should send templates.
</Warning>

Instagram, Messenger and Telegram have their own rules; the same principle applies.

## Conventions

* All request and response bodies are JSON.
* Timestamps are ISO 8601 UTC.
* IDs are UUIDs unless stated otherwise.
* Phone numbers are **E.164 without a `+`** — `201001234567`, never `01001234567`.
* Sends return `202 Accepted`: the message is queued, not yet delivered. Track the outcome
  through the message's `status` field.