A five-minute walkthrough from API key to delivered message, with curl examples you can paste straight into a terminal.
Getting a message out of the Esendex API takes three things: credentials, an account reference, and a POST request. Everything else is refinement.
Start by generating an API key from the web portal under Settings. Treat it like a password — it goes in an environment variable, never in your source tree, and never in a client-side bundle.
The dispatch endpoint accepts a JSON body containing the account reference, the recipient in international format, and the message body. A successful call returns a batch identifier, which is what you’ll use later to query delivery state. Note that a 2xx response means Esendex has accepted the message for delivery, not that it has arrived — those are different events, and conflating them is the most common mistake in a first integration.
From here, the natural next steps are handling delivery receipts and adding retry logic around transient failures.
