Test & activate
Every integration must pass a real activation test before it can go live. After you build an integration, test it and turn on the Live toggle.
Managed Vodafone integrations differ
BYO SMS here describes an integration you build and own. If Akedly operates a managed Vodafone integration for your account, several of the capabilities described below are fixed by Akedly and are not yours to set — see Managed Vodafone.
Run the activation test
Each integration card has a Test button and a Live toggle. Select Test to open the activation-test dialog.
Open the integration card and run its activation test.
This sends a real provider SMS
"It is a real send — your provider receives the request and may bill you at your provider's rate."
For a generic integration, the test costs one SMS at your provider's rate. Akedly does not charge the Own SMS platform fee for the test; the default 0.05 EGP fee applies per successful verification.
| Control | Effect |
|---|---|
| Test recipientphone number | The number shown under Send the test to. It is pre-filled and editable per integration. Editing only the test recipient never voids an already-passing test. On a managed Vodafone integration this field does not apply — the test always goes to a recipient Akedly configures, whatever you type here. |
| Run testbutton | Runs the request chain once against the test recipient. |
Coverage-scoped testing
The test recipient must be a number the integration covers.
Coverage is enforced before the test
The dialog lists the covered countries under the phone field. Run test is available as soon as you enter a number, but an out-of-coverage number is refused when you run it — the dialog shows which country the number is in and which countries the integration covers, and no test send happens. A managed Vodafone integration always tests against the recipient Akedly configures, whatever number you type.
| Control | Effect |
|---|---|
| Catch-allcoverage | "Covers all countries, so any valid number can test it." |
| Country-scopedcoverage | Enter a number from a covered country. For a Saudi Arabia integration, the dashboard says: "Only a number in Saudi Arabia (SA) can test this integration." |
When the test passes
A passing activation test makes the integration eligible to go live. A pass means every executed step returned a status in your Success status codes; the chain stops at the selected send step, so later steps are not run. It does not prove delivery, so — on an integration you built, where you choose the recipient — confirm the SMS actually arrived on that phone before going live. If your provider reports failures inside successful HTTP responses, a test can pass without a message arriving; see Verify provider success. On a managed Vodafone integration there is no chain of yours: the pass is Akedly's adapter completing the send, and the test always goes to the recipient Akedly configures rather than the number you entered.
Ready to activate
Turn on the Live toggle. The integration card then shows Active and "Last test passed — passed".
| Control | Effect |
|---|---|
| Passing teststatus | Confirms that the request chain completed successfully for the test recipient. |
| Livetoggle | Activates the integration after it passes the test. |
When the test fails
The failure dialog shows where the request chain stopped and what your provider returned, when a provider response was available.
| Control | Effect |
|---|---|
| Stepdiagnostic | The failed step number, HTTP method, and provider URL. |
| HTTP statusdiagnostic | The status returned by your provider, such as |
| Response bodydiagnostic | Your provider's response body when one was returned. Akedly redacts and truncates trace data, and transport or timeout failures may have no provider body. |
Common causes include invalid credentials, a response status outside your configured Success status codes, and network or timeout failures.
A failed re-test takes a live integration offline
If you re-test an active integration and the test fails, Akedly deactivates it. The integration must pass again before you can reactivate it.
Test limits
Activation-test limits
For generic integrations, Akedly limits activation tests to 20 per account per hour and 10 per account-and-number pair per hour. If you reach either limit, wait before trying again.
Re-test after changes
Configuration changes clear the passing test
Changes to the request chain, coverage, or secrets deactivate the integration and clear its passing test — and on a managed Vodafone integration, so does changing the approved sender name. Re-test it and turn Live back on before it can route again. Editing only the test recipient does not clear a passing test, and neither does editing only the name or description.
You're not done — enable it on a pipeline
Active does not mean routing
A passing, active integration sends no traffic until BYO SMS is also enabled for the pipeline.