Log in Sign up
First-party app
SOLAPI

SOLAPI

Send SMS, LMS, MMS and Kakao AlimTalk through SOLAPI, manage message groups and schedules, and read balance, sender numbers, statistics and Kakao channels and templates.

stable CommunicationMarketing

About

SOLAPI ships in the w6w first-party pack. It declares 22 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.

App id
io.w6w.solapi
Version
0.1.0
Author
w6w
Licence
MIT
Categories
Communication · Marketing

Overview

SOLAPI (솔라피) is a Korean messaging platform that sends SMS, LMS, MMS, Kakao AlimTalk and Brand Messages, RCS and more through one REST API. This app covers the messaging core a workflow needs: send a single message or a batch, send a Kakao AlimTalk template with variable substitution, and use SOLAPI’s group flow to assemble a large batch, schedule it, send it, or cancel it before it goes out.

It also reads the account state a sender depends on: the current balance and points, the registered sender numbers (Korean regulation requires a pre-registered caller ID), delivery status by message and by group, sending statistics for a date range, stored image files, and the Kakao channels and AlimTalk templates linked to the account.

SOLAPI signs every request with an HMAC-SHA256 Authorization header built from an API key, a fresh timestamp and a random salt. The app’s Auth sign hook builds that header for each request, so actions never see the API secret, and a connection test proves the key pair against the balance endpoint.

Build with SOLAPI

Three routes to the same 22 actions. The Workflow tab is generated from SOLAPI's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.

Add Messages to Group

add-group-messages

Add up to 10,000 messages to a PENDING group per call. Returns a per-message result with the assigned messageId and status code; errorCount above 0 means some messages failed validation.

Cancel Group Schedule

cancel-group-schedule

Cancel a SCHEDULED group. It returns to PENDING with its messages intact, so it can be edited or rescheduled.

Create Message Group

create-group

Create an empty message group (state PENDING). The first step of the group flow: add messages, then send or schedule it. Use it to assemble up to 1,000,000 messages across several calls.

Delete Message Group

delete-group

Delete a PENDING group; its messages are never sent. A group that has started sending cannot be deleted.

Get Balance

get-balance

Get the account balance and points in KRW, the auto-recharge settings and the low-balance alert configuration.

Get Message Group

get-group

Get one message group: its status, scheduled time, message counts and charge breakdown.

Get Kakao Channel

get-kakao-channel

Get one linked Kakao channel: handle, phone number, brand flag and shared accounts.

Get Kakao Template

get-kakao-template

Get one AlimTalk template: its content with #{placeholders}, buttons, review status and comments.

Get Sending Statistics

get-statistics

Get sending statistics for a date range: spend, refunds, totals and successes and failures by message type, with monthly and daily breakdowns.

List Active Sender Numbers

list-active-sender-numbers

List only the sender numbers that can send right now (status ACTIVE). Use it to pick a valid From for a send.

List Files

list-files

List files in SOLAPI storage (MMS images and the like) with their fileId, URL, size and dimensions. The fileId is what Send Message takes as Image ID. Cursor-paged.

List Group Messages

list-group-messages

List the messages inside one group, before or after sending. Cursor-paged.

List Message Groups

list-groups

List message groups (every send creates one), filtered by date range or advanced criteria. Cursor-paged.

List Kakao Channels

list-kakao-channels

List the Kakao channels linked to the account. A channel ID (pfId) is required to send AlimTalk.

List Kakao Templates

list-kakao-templates

List Kakao AlimTalk templates, filtered by channel, name or review status. Only APPROVED templates can be sent. Cursor-paged.

List Messages

list-messages

List sent and received messages with their delivery status, filtered by recipient, sender, group, type, status code or date range. History is kept 12 months. Cursor-paged.

List Sender Numbers

list-sender-numbers

List every sender number registered to the account with its status (PENDING, ACTIVE, INACTIVE, BLOCKED, DUPLICATED, EXPIRED, OVERLIMIT) and the registration limit.

Schedule Message Group

schedule-group

Schedule a PENDING group to send at a future time, from now up to 6 months out. Cancel with Cancel Group Schedule.

Send Kakao AlimTalk

send-alimtalk

Send one Kakao AlimTalk message from an approved template, filling its #{variable} placeholders. Optionally falls back to SMS/LMS if the AlimTalk fails (needs a registered sender number).

Send Message Group

send-group

Send a PENDING group now. The group moves to SENDING and can no longer be edited; delivery is asynchronous, so poll Get Message Group or use a webhook for results.

Send Message

send-message

Send one SMS, LMS or MMS. The type is detected from the text length (90 bytes or less is SMS, longer or with a subject is LMS, with an image is MMS) unless set. The sender number must be pre-registered.

Send Messages

send-messages

Send a batch of messages in one request (SMS, LMS, MMS, Kakao AlimTalk, RCS and others, each message carrying its own type). SOLAPI recommends the group flow above 10,000 messages. A message in failedMessageList was not sent even though the call succeeded.

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying SOLAPI's real ids. 

{
  "manifestVersion": "2",
  "name": "solapi-example",
  "steps": [
    {
      "id": "add-group-messages",
      "uses": {
        "app": "io.w6w.solapi",
        "action": "add-group-messages",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "groupId": "<groupId>",
        "messages": "<messages>"
      }
    }
  ]
}

Here are some of the things you can do

  • Add Messages to Group

    perform
    add-group-messages

  • Create Message Group

    perform
    create-group

  • Get Balance

    read
    get-balance

  • Get Message Group

    read
    get-group

  • Get Kakao Channel

    read
    get-kakao-channel

+17 more actions available

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for SOLAPI, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to SOLAPI. The Workflow tab is where this app's real ids are.

Install 
npm install @w6w/sdk
yarn add @w6w/sdk
pnpm add @w6w/sdk
deno add npm:@w6w/sdk
Code 
import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "add-group-messages",
  payload: {
    groupId: "<value>",
    messages: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);
Install the CLI 
npm install -g @w6w/cli
CLI 
w6w run conn_YOUR_CONNECTION_ID --action add-group-messages --payload '{"groupId":"<value>","messages":"<value>"}'

Give an AI agent SOLAPI — without giving it SOLAPI's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

One tool call 
{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.solapi#add-group-messages",
    "input": {
      "groupId": "<groupId>",
      "messages": "<messages>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's SOLAPI connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

Credentials it can't read

The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.

A tool surface scoped to the caller

Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.

A durable workflow in one call

Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.

Health-aware discovery

SOLAPI's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.

The MCP surface is part of the hosted platform. SOLAPI itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access

Health checks

SOLAPI declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

SOLAPI platform status

dependency

API reachable

Unauthenticated GET https://api.solapi.com/cash/v1/balance. A 401 carrying SOLAPI's JSON `{errorCode, errorMessage}` passes — it proves the API and its auth layer are answering. Credential validity is the derived `auth:*` check's job.

quota

Prepaid balance

Signed GET /cash/v1/balance: account balance and points in KRW. Zero balance and zero points is degraded (post-paid accounts can still send).