Your First Steps with the Rapisign API

All a developer needs to fire off a first document notification inside half an hour — authentication, request structure, and delivery tracking.

There are three things to get working, and they are best taken in order: prove you can authenticate, send one notification to your own handset, then read the status back. Nothing else matters until those three succeed.

1. Authenticate

Create a free account and copy the API key from your dashboard. Keys are per environment, so keep the test key out of production code and store both outside your repository. Every request to the gateway carries the key in its authorization header over an encrypted connection.

2. Send one notification

A request needs a recipient number in international format, the template you want, and the values that fill its placeholders. Send it to your own phone first. A successful call returns an identifier — hold on to it, because that is how you ask about the message later.

3. Track delivery

Status moves from accepted to sent to delivered, and the gateway reports each change as it happens. Register a webhook so your own system hears about it without polling, and store the final state against whatever record triggered the notification.

Then harden it

Retry on transport failures but not on rejections. Log the identifier alongside your own reference so support can trace a message in one step. Keep templates in one place rather than scattered through your codebase. None of this takes long, and it is far easier before your first busy day than after it.