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

Verta StageService API

The StageService API from Verta — 9 operation(s) for stageservice.

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

Tagged areas include StageService. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 9 operations across 9 paths, and defines 21 schemas. It is described by OpenAPI 2.0, at version version not set.

Requests are made against the base URL https://docs.verta.ai/.

9 operations 9 paths 21 schemas 9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
version not set
Base URL
https://docs.verta.ai/
Resource Areas
1

Paths & Operations 9

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

StageService 9
POST
/stage/approveTransition
StageService_ApproveTransition 1 param → 200default
POST
/stage/closeTransition
StageService_CloseTransition 1 param → 200default
POST
/stage/commitTransition
Only a transition that has been approved can be commited. The user must have RW permission Similar to merging a PR
StageService_CommitTransition 1 param → 200default
POST
/stage/createComment
StageService_CreateComment 1 param → 200default
POST
/stage/createTransition
Anyone with RW permission on the model version can do any of these Note that the author of the transition cannot approve or reject it themselves (like in github)
StageService_CreateTransition 1 param → 200default
POST
/stage/findActivities
List objects from the db. Similar to the PR history
StageService_FindActivities 1 param → 200default
POST
/stage/findTransitions
Similar to listing PRs by state
StageService_FindTransitions 1 param → 200default
POST
/stage/rejectTransition
StageService_RejectTransition 1 param → 200default
POST
/stage/updateStage
Directly update the stage without going through approval. The user must have RW permission Similar to merging to master directly
StageService_UpdateStage 1 param → 200default

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are registryActivity (11 properties), registryTransition (4 properties), runtimeError (4 properties), registryFindTransitionsRequest (3 properties). Each schema is shown below with its type and property counts.

registryCloseTransitionRequest
object
2 properties
registryStageUpdate
object
1 property
protobufAny
object
2 properties
runtimeError
object
4 properties
StageEnumStage
string
registryFindTransitionsRequestResponse
object
1 property
registryApproveTransitionRequest
object
2 properties
registryTransition
object
4 properties
registryRejectionOfTransition
object
registryCloseOfTransition
object
registryFindTransitionsRequest
object
3 properties
registryCreateCommentRequest
object
2 properties
registryApprovalOfTransition
object
registryFindActivitiesRequest
object
2 properties
registryActivity
object
11 properties
registryUpdateStageRequest
object
3 properties
registryRejectTransitionRequest
object
2 properties
registryCreateTransitionRequest
object
3 properties
registryFindActivitiesRequestResponse
object
1 property
TransitionStateEnumTransitionState
string
registryCommitTransitionRequest
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

verta-stageservice-api-openapi.yml Raw ↑

Other APIs Verta publishes across the network.

Verta AuthzService API
Verta DatasetService API
Verta ExperimentRunService API
Verta ExperimentService API
Verta MonitoredEntityService API
Verta ProjectService API
Verta RegistryService API
Verta SCIMConfigurationService API
Verta UACService API
Verta VersioningService API
Where this information came from

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