Assertible Deployments API

Name: Assertible Deployments API API
Brand: Assertible Deployments API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting Qabasic1 EndpointsREST

For Agents

Trigger Assertible test runs by creating or updating a deployment record after a CI/CD pipeline finishes deploying.

Quickstart

Get started with Assertible Deployments API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"trigger an Assertible test run after a deploy"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Assertible Deployments API API.

Trigger an Assertible test run by creating a deployment record

Update an existing deployment to associate it with a new commit or environment

Connect a CI/CD pipeline to automated post-deploy verification

Tag a test run with environment metadata such as 'staging' or 'production'

GET STARTED

Start building with Assertible Deployments API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Assertible Deployments API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Assertible Deployments API, keeping it validated and agent-ready. Assertible is an automated API testing service that runs continuous tests against web services. The Deployments API exposes a single POST endpoint that creates or updates a deployment record, which in turn triggers the configured test suite to run against that environment. Authentication is via HTTP basic auth using the Assertible API token. This API is purpose-built for CI/CD integration where every deploy should immediately be validated.

Use Cases

Patterns agents use Assertible Deployments API API for, with concrete tasks.

★ Post-Deploy Verification from CI/CD

Wire POST /deployments into the final step of a CI/CD pipeline so every deploy automatically triggers the Assertible test suite for that environment. The endpoint accepts the service identifier and environment context, and Assertible runs the configured smoke and regression tests against the live URL. Removes the manual 'remember to kick off tests' step after a release.

Call POST /deployments after a successful production release with environment='production' and commit SHA, then surface the test-run URL

Multi-Environment Test Gating

Use the same /deployments endpoint to record deploys to staging, QA, and production separately, so each environment has its own test history. Agents can read CI logs and call POST /deployments for the right environment, giving the QA team a clear timeline of when each environment was last validated.

Call POST /deployments for the staging environment after the staging pipeline finishes, then again for production after the prod release

AI Agent for Release Validation

An agent integrated through Jentic can listen for deploy events on a CI platform, call POST /deployments to trigger Assertible tests, and report results back to the release channel — without holding the Assertible API token. Jentic stores the basic-auth credential in its vault and the agent calls the deployment endpoint by intent.

Through Jentic, listen for GitHub deployment events, call POST /deployments on Assertible for each, and post the test result link back to the PR

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for assertible deployments api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/deployments

Create or update a deployment to trigger a test run

POST

/deployments

Create or update a deployment to trigger a test run

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Assertible API tokens are stored encrypted in the Jentic vault as a basic-auth credential. Agents receive scoped execution access — the token is never exposed in prompts, logs, or agent memory and is injected as the basic-auth Authorization header at execution time.

Intent-based discovery

Agents search Jentic for 'trigger a post-deploy test run' and Jentic returns POST /deployments with its input schema, so the agent does not need to know the Assertible URL or basic-auth convention in advance.

Time to first call

Direct Assertible integration: a couple of hours to wire basic auth and the deployment payload from a CI step. Through Jentic: under 10 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

BrowserStack

BrowserStack runs cross-browser and device tests; Assertible focuses on API contract and uptime tests.

Choose BrowserStack for UI and cross-browser testing; pick Assertible when post-deploy API contract checks are the requirement.

Alternative

Runscope

Runscope (now part of BlazeMeter) covers API monitoring and testing similar to Assertible.

Choose Runscope when synthetic monitoring is bundled with API testing; pick Assertible for lightweight CI-triggered post-deploy checks.

Complementary

GitHub API

GitHub deployment events naturally trigger Assertible deployments via the GitHub Actions or webhook integration.

Pair with Assertible when a GitHub workflow finishes a release and the next step should be a deploy-triggered test run.

Complementary

CircleCI

CircleCI pipelines can call POST /deployments as the final job of a release workflow.

Use CircleCI alongside Assertible when the build/test/deploy pipeline lives in CircleCI and post-deploy verification needs to be triggered automatically.

FAQs

Specific to using Assertible Deployments API API through Jentic.

Why is there no official OpenAPI spec for Assertible Deployments API?

Assertible documents this endpoint in their guide rather than as a published OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Assertible Deployments API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Assertible Deployments API use?

The API uses HTTP basic authentication. The Assertible API token is supplied as the username with an empty password. Jentic stores the credential in its vault and constructs the basic-auth Authorization header at execution time.

What does POST /deployments do?

POST /deployments creates or updates a deployment record for a specific Assertible service and environment. Creating the record triggers the test suite configured for that service against the live URL. The response includes the deployment ID and a link to the test-run results.

Can I trigger Assertible tests from any CI provider?

Yes. POST /deployments is provider-agnostic — call it from GitHub Actions, GitLab CI, CircleCI, Jenkins, or any other system after the deploy step succeeds. Pass the environment and commit metadata in the request body to keep the test history traceable.

What are the rate limits for the Assertible Deployments API?

The OpenAPI specification does not publish explicit rate limits. The endpoint is intended to be called once per deploy, so volume is naturally low. Implement exponential backoff on HTTP 429 responses if a misconfigured pipeline triggers it more often than expected.

How do I trigger a deployment test run through Jentic?

Search Jentic for 'trigger an Assertible test run after a deploy' — POST /deployments will be returned. Load the operation schema, supply the service ID, environment, and commit details, and execute. Jentic handles the basic-auth credential and returns the deployment ID for downstream tracking.