SagoAPI

One API for OTP, email and payments

Connect once, and use one key for each service, with no separate contract for each provider.

Currently offered in Vietnam. Based elsewhere? Talk to us and we’ll look at it together. The activation date for each service is set in your contract.

POST /v1/otp/sendAuthorization: Bearer ••••••••X-Client-Id: your-brandIdempotency-Key: 7f3a-91c2{"phone": "+84912345678","code": "482913"}

200 OK{ "id": "0190b7e2-…", "status": "succeeded" }

POST /v1/mail/sendAuthorization: Bearer ••••••••X-Client-Id: your-brandIdempotency-Key: b81d-40e6{"to": "[email protected]","subject": "Your receipt","text": "Thanks for your order."}

200 OK{ "id": "0190b7e3-…", "status": "succeeded" }

POST /v1/payments/checkoutsAuthorization: Bearer ••••••••X-Client-Id: your-brandIdempotency-Key: c27e-55af{"orderId": "A-10482","amount": 250000,"description": "Order A-10482"}

200 OK{ "paymentUrl": "https://pay.yourbrand.com/…" }

What you can send

OTP

You create and check the code. We deliver it and never store it.
Sent under your own brand name.
Can try Zalo first and fall back to SMS.

Email

Receipts, notices, password resets

Sent from your own domain.
Made for transactional email, not bulk campaigns.

Payments

Checkout links for online payments

Create a checkout link and get the result back by callback.
Money goes straight to your account. SagoMind never holds it.

Three ways to use it

Choose separately for each service.

Our provider account
You want to move fast and don’t have a provider yet.
Your account, through SagoAPI
You already have a contract with a provider.
Direct connection
Your internal rules don’t allow data to pass through a third party.

Built for the days things go wrong

Retry without worry

Send again with the same Idempotency-Key and you get the first result back, with no second message and no second charge.

One key, one service

Each key works for one service, so a leaked email key can’t touch your payments.

Change keys with no downtime

Two keys can be live at once. Switch to the new one, then revoke the old.

A limit on every key

Requests per minute are capped per key, so a leak can’t empty your balance in minutes.

Nothing sensitive in the logs

We keep a masked recipient. OTP codes and message content are never stored.

From sign-up to first request

Sign up

Create an account and choose the services you need.

We review

We approve each service and set your price.

Get your key

Create a key in the console. It shows once, so keep it safe.

Send a request

Top up your balance, add the key to your app and start sending.

A console for your team

Keys and connection details
Balance and top-up history
A log of every request, by month, service and status
Monthly costs, with a CSV for reconciling

How you pay

Pay per use from a prepaid balance.

Each request keeps the price at that moment, so a price change never rewrites past usage.

Pricing depends on your scope. We’ll send a quote after we talk.

The provider takes the requestCharged
The result isn’t known, such as a timeoutCharged
The provider refusesNo charge
You retry with the same Idempotency-KeyNo charge
Bad data, a wrong key, over the limit or not enough balanceNo charge

Need these for your own application?

Let’s talk.

Talk to us