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

One Codex Controls API

The Controls API from One Codex — 9 operation(s) for controls.

One Codex Controls API is one of 25 APIs that One Codex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Controls. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 10 operations across 9 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version v1.

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

10 operations 9 paths 1 schemas 1 DELETE7 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://app.onecodex.com/api/v1/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

One Codex Controls API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (apiKeyAuth). By default, every request must be authenticated.

Paths & Operations 10

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

Controls 10
GET
/api/v1/controls
GET controls instances
get_controls_instances 4 params → 200
GET
/api/v1/controls/public
GET controls instancespublic
get_controls_instances_public 4 params → 200
GET
/api/v1/controls/{id}
GET controls
get_controls_self 1 param → 200
POST
/api/v1/controls/{id}/cancel
POST controls cancel
post_controls_cancel 1 param → 200
GET
/api/v1/controls/{id}/file_details
GET controls filedetails
get_controls_file_details 1 param → 200
DELETE
/api/v1/controls/{id}/files
DELETE controls files
delete_controls_files 1 param → 204
GET
/api/v1/controls/{id}/files
GET controls files
get_controls_files 1 param → 200
GET
/api/v1/controls/{id}/logs
GET controls logs
get_controls_logs 2 params → 200
POST
/api/v1/controls/{id}/rerun
POST controls rerun
post_controls_rerun 1 param → 200
GET
/api/v1/controls/{id}/results
GET controls results
get_controls_results 1 param → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is controls (9 properties). Each schema is shown below with its type and property counts.

controls
object
9 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

one-codex-controls-api-openapi.yml Raw ↑

Other APIs One Codex publishes across the network.

One Codex Account API
One Codex Alignments API
One Codex Analyses API
One Codex Annotation Sets API
One Codex Assemblies API
One Codex Assets API
One Codex Classifications API
One Codex Documents API
One Codex Events API
One Codex Functional Profiles API
One Codex Genomes API
One Codex Jobs API
Where this information came from

This is an independent, third-party profile of One Codex Controls 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.