Georgian first, English too
Every message template is written in Georgian and English, and Georgian text is measured exactly, so you know how many segments each code costs.
Private beta · Transactional SMS API for Georgia
Send verification, sign-in, and password-reset codes through a focused API, in Georgian or English, with honest message status. Or let NOTIFY make the code and check it for you.
curl --request POST \
--url https://api.n0t1fy.dev/v1/messages \
--header 'Authorization: Bearer sk_test_…' \
--header 'Idempotency-Key: 8b671…' \
--data '{
"to": "+995591234567",
"template": "verification_code",
"variables": { "code": "482913" }
}'
{ "id": "msg_01J…", "status": "submitted" }
Made for the codes your product has to send.
A small, deliberate surface
Local SMS delivery should not require an integration project of its own. NOTIFY keeps the public contract narrow so the important parts are obvious.
Use a project-scoped test key and the fake provider. Your integration can be verified without sending a real SMS.
Pick a template, fill in the code, and send it with a familiar JSON request and an idempotency key that protects retries.
submitted means provider acceptance. delivered is used only after reliable provider confirmation.
Built for the real integration
Every message template is written in Georgian and English, and Georgian text is measured exactly, so you know how many segments each code costs.
Provider acceptance and final delivery are distinct states. Your product gets a useful status without a misleading claim.
Start a verification and NOTIFY makes a six-digit code, sends it and checks what the user types: ten minutes, five attempts, once. Only approved lets anyone in.
Project-scoped keys, masked recipient responses, encrypted stored text, rate limits, and redacted logs are part of the baseline.
What you can send
Codes, to any Georgian mobile number: verification, sign-in and password-reset codes. Team alerts, to your own confirmed team only: a service down or up again, an urgent incident or support ticket, a failed job, your agent's updates. Each number is confirmed with a code on your dashboard, so an alert never reaches a stranger.
Humans and agents welcome
The API follows conventions developers and coding agents already know: bearer keys, JSON, predictable REST routes, idempotency, and repair-oriented errors.
Pricing
Test keys cost nothing. Real SMS come with one monthly subscription, priced in GEL with VAT included.
0 GEL
To build and try your integration.
20 GEL / month
VAT included.
Every template fits in one SMS, in Georgian or English. A verification, where NOTIFY makes the code and checks it, costs the one SMS that carries the code; checking is free. A month runs from the day your payment arrives. Billing is by bank transfer for now, and the subscription does not renew by itself: you pay for each month.
No surprises in the fine print
No. The private beta sends three transactional messages that the recipient is expecting: a verification code, a sign-in code, and a password-reset code.
Not yet. Every message comes from a built-in template, and you fill in its blanks: a code, a number, or a name from a list, never free words. That is what keeps the shared sender NOTIFY trustworthy: nobody can send arbitrary text under it. Besides codes to any number, there are team alerts (a service down or up again, a failed job, an urgent incident or ticket, your agent's updates), which go only to numbers confirmed on your own team. Every template is on /templates. If you need another kind of message, tell us at contact@n0t1fy.dev.
Yes. Start a verification with POST /v1/verifications: NOTIFY makes a six-digit code and sends it. Check what the user types with POST /v1/verifications/{id}/check; only a 200 with status approved lets the user in. The code itself is never stored, only a keyed hash of it until the verification ends (at most about an hour after the code expires). With a test key, the test numbers always get 000000. See Verifications.
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.
Yes. Test API keys use a fake provider and never send a real message or use live SMS balance.
Yes. Sign in with GitHub or Google at /login to create test and live keys yourself; a new account starts with free SMS credits. An AI coding agent can get a test key with no account at all: POST /v1/test-keys, or the create_test_key tool of the MCP server.
Private beta
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.