Triggering tests via API

mabl has a Deployment Events API endpoint that you can use to trigger tests via API. This is particularly useful for integrating with your preferred CI/CD tools, including Jenkins.

Reviewing the API settings for your workspace

  1. Click "Settings" in the left-hand navigation menu.
  2. Locate and click on the "API Keys" tab. In that section, you'll see the API key for your workspace.
  3. Scroll down to the "API documentation" section, click "Select an API," then click "Deployment Events API."

In that section, you'll see need to add the environment and application you'd like to trigger on deployment.

Execution Results API

Visit our Execution Results API documentation to learn more about integrating mabl with your existing CI/CD pipeline.

Previewing the Deployment Event

You can perform a preview (dry run) of a Deployment Events API call to see what plans would have executed, without actually running them. Use this to quickly fine-tune your configuration and test your integration.

  1. Select your target environment and application from the fields.
  2. Once added, you'll see additional fields, instructions, and a CURL command builder that you can use to understand the required format to trigger tests via the Deployment Events API.
  1. Select and copy the CURL command.
  1. Open a terminal window on your machine
  2. Paste the CURL command into the terminal
  3. Replace the URL with https://api.mabl.com/events/deployment?preview=true
  4. Hit Enter
  5. Confirm that you received a successful response, similar to the following:
{"id":"ewew-b7d3-dafd-81e4-fddfafdwew","environment_id":"dfasad-wewrfe42-645df-b94d-ff78011828ad","application_id":"42424-fda-fa-fdafda-233224dazrw","received_time":1513266635798}

Deployment Events API Webinar

Watch this webinar featuring mabl's Matthew Stein and James Baldassari for a detailed look at the deployment events API and how to incorporate it into your mabl plans.

Triggering tests via API


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.