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

Qase suites API

Test suites that group and organize test cases.

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

Tagged areas include Suites. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 5 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.qase.io/v1.

5 operations 2 paths 6 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.qase.io/v1
Authentication
API Key
Contact
License
Resource Areas
1

Authentication & Security 1

Qase suites API declares 1 security scheme for authenticating requests. An API key is passed in the header as Token (TokenAuth). By default, every request must be authenticated.

  • TokenAuth — A personal or application API token. Create it in the Qase app under Settings and pass it in the Token header on every request. All requests must use HTTPS.

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

suites 5

Test suites that group and organize test cases.

GET
/suite/{code}
Get all test suites
get-suites 3 params → 200401429
POST
/suite/{code}
Create a new test suite
create-suite 1 param body → 200401422429
GET
/suite/{code}/{id}
Get a specific test suite
get-suite 2 params → 200401404429
PATCH
/suite/{code}/{id}
Update a specific test suite
update-suite 2 params body → 200401404429
DELETE
/suite/{code}/{id}
Delete a specific test suite
delete-suite 2 params → 200401404429

Schemas 6

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

SuiteResponse
object
2 properties
IdResponse
object
2 properties
SuiteCreate
object
4 properties 1 required
SuiteListResponse
object
2 properties
Suite
Error
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qase-suites-api-openapi.yml Raw ↑

Other APIs Qase publishes across the network.

Qase cases API
Qase defects API
Qase plans API
Qase projects API
Qase results API
Qase runs API
Where this information came from

This is an independent, third-party profile of Qase suites 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.