Send SMS with AWS Lambda

Send a text from an AWS Lambda function (Node.js runtime) with the TextKit SDK.

Prompt for your AI agent

Paste this into Claude Code, Cursor or any coding agent to have it do the integration:

text
Add SMS sending to this AWS Lambda project with TextKit.

- Docs for this stack: https://jointextkit.com/docs/send-with-aws-lambda.md
- API: POST https://api.jointextkit.com/v1/messages with `Authorization: Bearer
  <key>` and a JSON body `{"to": "+1...", "body": "..."}`.
- Use the official SDK: bundle `jointextkit` with the function, set
  `TEXTKIT_API_KEY` in its environment, then `new TextKit().messages.send({ to,
  body })`.
- Read the key from the `TEXTKIT_API_KEY` environment variable. Never hardcode
  it or send it to the browser.
- Phone numbers are E.164 and US or Canada only (`+1` followed by 10 digits).
- A test key (`ssms_sk_test_`) simulates: `+15005550006` always ends `delivered`
  and no phone gets a text.
- Errors are JSON: `{"error": {"code", "message", "param"}}` with a 4xx status.
  On `429`, wait `Retry-After` seconds and retry.
- Send only from server code that runs after a real event (a signup, an order).
  Never expose an endpoint that texts any number a visitor types.

Before you start

  • An API key. Create a free account and copy the test key (ssms_sk_test_...) from Home in the console. It works at once, no card.
  • A Lambda function on the Node.js 18 runtime or later.
  • Put the key in an environment variable:
bash
export TEXTKIT_API_KEY=ssms_sk_test_...

1. Install the SDK

bash
mkdir send-sms && cd send-sms
npm init -y && npm install jointextkit

2. Write the handler

Create index.mjs:

javascript
import { TextKit } from 'jointextkit';

const sms = new TextKit(); // reads TEXTKIT_API_KEY from the function's environment

export const handler = async (event) => {
  const { to, body } = typeof event.body === 'string' ? JSON.parse(event.body) : event;
  const message = await sms.messages.send({ to, body });
  return { statusCode: 200, body: JSON.stringify({ id: message.id, status: message.status }) };
};

3. Deploy it

bash
zip -r function.zip index.mjs node_modules package.json
aws lambda update-function-code --function-name send-sms --zip-file fileb://function.zip
aws lambda update-function-configuration --function-name send-sms \
  --environment "Variables={TEXTKIT_API_KEY=ssms_sk_test_...}"

Invoke it with {"to": "+15005550006", "body": "Hello from TextKit"} as the test event. It returns {"id": "msg_...", "status": "delivered"}.

What the test key did

+15005550006 is a sandbox number: the send comes back delivered and no phone gets a text (the response says "simulated": true). Put your own verified phone in to and the test key texts it for real. See Sandbox & test numbers.

Handle errors

The SDK throws a TextKitError with the API's code, status and message (plus param for a bad field and retryAfter on a rate limit). It retries network failures and 429s for you, with an idempotency key, so a retry never sends twice.

StatusCodeWhat to do
400invalid_requestA field is missing or malformed; param names it.
401invalid_api_keyThe key is missing, revoked or mistyped.
402insufficient_creditsAdd credits; nothing was sent or charged.
403recipient_opted_outThey texted STOP. Do not retry.
429rate_limitedWait Retry-After seconds, then retry.

Every code is in Errors.

Go live

  1. Add a number in the console.
  2. Register your use case. We file your 10DLC registration; toll-free numbers use a guided verification form. Until carriers approve it, the number texts only your verified numbers. See Compliance & registration.
  3. Swap in a live key (ssms_sk_live_...). The code stays the same.

Next steps

  • Webhooks: delivery receipts and replies, pushed to your server.
  • Verify: one-time codes in two calls, billed only when verified.
  • Send an SMS: every field the endpoint takes.
  • All quickstarts: the same guide for other languages and frameworks.