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

# Prerequisites

> Set up your Multicountry SMS account and obtain credentials before sending messages.

Multicountry SMS uses the same Beem sign-up flow as [local SMS](/guides/sms/prerequisites). After your first login, enable international messaging on your account.

***

## Steps to get started

<Steps>
  <Step title="Create a Beem account">
    Register at [login.beem.africa](https://login.beem.africa/) and verify your email address and phone number.
  </Step>

  <Step title="Enable Multicountry SMS">
    On first sign-in, select the option to **send SMS to multiple countries** (or contact [support@beem.africa](mailto:support@beem.africa) to enable international coverage on your account).
  </Step>

  <Step title="Account configuration">
    Your account manager configures countries, coverage, and test credits. You receive **USERNAME** and **PASSWORD** credentials for the Messaging Platform HTTP API and/or SMPP.
  </Step>

  <Step title="Start sending">
    Once your account has credits and credentials, send messages via the [HTTP API](/guides/multicountry-sms/sending-messages) or [SMPP](/guides/multicountry-sms/smpp).
  </Step>
</Steps>

***

## Credentials

<Info>
  Multicountry SMS uses a **legacy authentication model** — not the standard Beem API Key, Secret, or access token used by local SMS, OTP, Airtime, and other products.
</Info>

The HTTP send API authenticates each request using form parameters:

| Parameter  | Description                       |
| ---------- | --------------------------------- |
| `USERNAME` | Account username provided by Beem |
| `PASSWORD` | Account password provided by Beem |

The balance API uses **HTTP Basic Authentication** with the same username and password.

<Warning>
  Keep your credentials secure. Do not expose them in client-side code or public repositories.
</Warning>

***

## Delivery reports and inbound SMS

You do **not** need a separate portal callback configuration step for delivery reports. Set the **`DLRADDRESS`** parameter on each outbound HTTP send request to receive DLRs at your HTTPS endpoint.

For **inbound two-way SMS** on Multicountry accounts, callback URLs are configured manually by the Beem team — see [Inbound two-way SMS](/guides/multicountry-sms/inbound-two-way).