Private beta · Transactional SMS API for Georgia

Transactional SMS for Georgia, built for developers.

Send verification codes, alerts, confirmations, and receipts through a focused API with Georgian/Unicode support and honest message status.

Read the API reference See how it works

Georgian / ქართული Unicode ready
Test safely before live delivery
Clear, normalized message states

send-message.sh

curl --request POST \
  --url https://api…/v1/messages \
  --header 'Authorization: Bearer sk_test_…' \
  --header 'Idempotency-Key: 8b671…' \
  --data '{
    "to": "+995591234567",
    "template": "verification_code",
    "variables": { "code": "482913" }
  }'

201 Created { "id": "msg_01J…", "status": "submitted" }

Made for the messages your product has to send.

Verification codes
Security alerts
Booking confirmations
Receipts & updates

A small, deliberate surface

One API. The essential workflow.

Local SMS delivery should not require an integration project of its own. Geo SMS Hub keeps the public contract narrow so the important parts are obvious.

01
Build safely

Use a project-scoped test key and the fake provider. Your integration can be verified without sending a real SMS.
02
Send one message

Create a transactional message with a familiar JSON request and an idempotency key that protects retries.
03
Read an honest status

submitted means provider acceptance. delivered is used only after reliable provider confirmation.

Built for the real integration

The details developers end up caring about.

Georgian text, end to end

Send UTF-8 and Georgian/Unicode text without treating local language support as an exception.

Status without wishful thinking

Provider acceptance and final delivery are distinct states. Your product gets a useful status without a misleading claim.

Sensible defaults

Project-scoped keys, masked recipient responses, encrypted stored text, rate limits, and redacted logs are part of the baseline.

Humans and agents welcome

Clear enough to integrate in one focused session.

The API follows conventions developers and coding agents already know: bearer keys, JSON, predictable REST routes, idempotency, and repair-oriented errors.

Developer API reference Agent integration guide OpenAPI document

No surprises in the fine print

A focused beta, with clear boundaries.

Is this for marketing campaigns or bulk SMS?

No. The private beta is for transactional, recipient-expected messages from applications.

Does submitted mean the recipient received the SMS?

No. It means the delivery provider accepted the request. delivered is used only after a reliable provider confirmation.

Can I test without sending a real SMS?

Yes. Test API keys use a fake provider and never send a real message or use live SMS balance.

Can I sign up and get a key myself?

Not yet. Access is currently arranged directly so every private-beta integration can be supported closely.

Private beta

Help shape the developer API for transactional SMS in Georgia.

We are inviting a small group of teams with a real transactional SMS use case. The goal is to learn from a complete integration—not to promise a platform before it exists.

Explore the API