Skip to main content
1

Create an account

account.signup needs no key — it is how you get one. It creates an account, a project, and live and test environments, and returns a secret and a publishable key for each: live.key, live.publishableKey, test.key and test.publishableKey.The keys are returned once and never again by any operation, so store them before the next call. They work immediately. The owner seat in the dashboard activates when you follow the link the call emails; nothing below waits for that.
2

Send an email

Export live.key as LATH_API_KEY and send to your own address. With no from, the message goes out from the project’s own sender, no-reply@<project-slug>.via.trylath.com, which is authenticated already — there is no domain to verify first.A send with no topic is transactional, so consent is not asked for; only a suppression (a bounce, a complaint, a manual block) would stop it. Read status on the reply: queued means it is on its way, suppressed means it was stored and not sent, with the reason beside it.Use the live key for this. A lath_test_ key only emails members of your account who have accepted their seat, and the owner seat is not accepted until you follow that link.
3

Where to go next

Text messages are the one channel that cannot send on day one: sms.send stores the message and answers with a blocked object until a carrier registration is active and the environment has a number. Send your first text explains why, and what to file.To sign users in, start with Sign in your first user. To connect a coding agent instead of writing the calls yourself, For agents has the exact setup for each one.
Last modified on September 23, 2026