kudosity-setuplisted

# Get set up with Kudosity Everything needed before the first message sends. Four things have to be true: 1. A Kudosity account exists 2. API credentials are in the environment 3. The right credential is used for the right API 4. A **sender** is available to send from Steps 1–3 are the usual focus. **Step 4 is the one that's missed** — credentials can be perfectly valid and a send still fails because there's nothing to send *from*. ## 1. Account If the person has no account, direct them to **https://kudosity.com/signup**. Account creation is not available through the API — it happens in a browser. An agent can't complete this step on someone's behalf; hand them the link and wait. ## 2. Find the credentials Once signed in: **Developers → API Settings**. | Credential | Environment variable | Needed for | |---|---|---| | API Key | `KUDOSITY_API_KEY` | Everything | | API Secret | `KUDOSITY_API_SECRET` | The V1 API only — contacts, lists, bulk SMS, reporting, balance | If the API Secret field is blank, it hasn't been generated yet. It has to be created in the dashboard before V1 calls will work — there's no API to mint one. ## 3. Which credential for which API Kudosity runs two APIs. This is the single biggest source of confusion, and a 401 is almost always this. | | Base URL | Auth | |---|---|---| | **V2** — single-recipient SMS, MMS, WhatsApp, RCS, webhooks | `api.transmitmessage.com` | Header `x-api-key: {KUDOSITY_API_KEY}` | | **V1** — contact lists, bulk/list sen