Akedly

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.


Run the activation test

Each integration card has a Test button and a Live toggle. Select Test to open the activation-test dialog.

View in dashboardChannels → Setup → BYO SMS Setup

Open the integration card and run its activation test.

  • Name
    Test recipient
    Type
    phone number
    Description

    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.

  • Name
    Run test
    Type
    button
    Description

    Runs the request chain once against the test recipient.


Coverage-scoped testing

The test recipient must be a number the integration covers.

  • Name
    Catch-all
    Type
    coverage
    Description

    "Covers all countries, so any valid number can test it."

  • Name
    Country-scoped
    Type
    coverage
    Description

    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.

  • Name
    Passing test
    Type
    status
    Description

    Confirms that the request chain completed successfully for the test recipient.

  • Name
    Live
    Type
    toggle
    Description

    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.

  • Name
    Step
    Type
    diagnostic
    Description

    The failed step number, HTTP method, and provider URL.

  • Name
    HTTP status
    Type
    diagnostic
    Description

    The status returned by your provider, such as 401 for invalid credentials.

  • Name
    Response body
    Type
    diagnostic
    Description

    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.


Test limits


Re-test after changes


You're not done — enable it on a pipeline

Was this page helpful?