How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Assertible API

Assertible's public programmatic surface, used to drive test runs from a CI/CD pipeline. It consists of two documented POST operations on assertible.com: a trigger URL that runs a web service's tests (POST /apis/{serviceId}/run) and a sync call that re-imports an OpenAPI, Swagger or Postman specification and updates the tests derived from it (POST /imports/{importId}/sync). Both authenticate with HTTP Basic using an Assertible API token as the username. There are no read operations: web services, tests, imports, environments, schedules and alert hooks are created and listed in the dashboard only. Assertible's own /docs/api page states the broader API is "under construction".

Assertible API is one of 2 APIs that Assertible publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include API Testing, Monitoring, and Quality Assurance. The published artifact set on APIs.io includes API documentation, a getting-started guide, an API reference, and an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against a single base URL, https://assertible.com.

1 operations 1 paths 2 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Base URL
https://assertible.com
Authentication
HTTP Basic
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

Assertible API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth).

  • basicAuth — HTTP Basic auth where the username is the Assertible API token (ASSERTIBLEAPITOKEN) and the password is left empty.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Triggers 1

Run a web service's tests on demand from outside the dashboard

POST
/apis/{serviceId}/run
Run the tests for a web service
runWebServiceTests 6 params body → 200401404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are TriggerRunRequest (5 properties), Error (2 properties). Each schema is shown below with its type and property counts.

TriggerRunRequest
object
Trigger URL parameters, as documented in the Trigger URL Parameters table.
5 properties
Error
object
The Assertible error envelope.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

assertible-triggers-api-openapi.yml Raw ↑

Other APIs Assertible publishes across the network.

Assertible Deployments API
Where this information came from

This is an independent, third-party profile of Assertible API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.