Skip to main content

Corva API

The Corva API is the programmatic interface to data and resources available in the Corva platform. Customers use it to connect external systems, build analytics and exports, automate workflows, and power Dev Center applications without manually retrieving information through the Corva user interface. The Platform API provides wells and their operational relationships; the Data API provides the time-, depth-, completion-, and reference-based dataset records associated with those assets. Most integrations use both APIs: first identify an asset, then query its data.

Customer integrations use the Platform API to identify wells and assets, then use the asset ID with the Data API to access operational data.

Start hereMake your first requestFind a well, get its asset ID, and retrieve a dataset record.Platform APIFind wells and assetsDiscover the IDs and metadata needed for later data queries.Data APIRead operational dataFilter, sort, page through, and select fields from a dataset.Real timeReceive new dataCombine an initial request with a live subscription.

Which API do I use?​

You want to…Use
Find wells, rigs, programs, pads, frac fleets, or drillout unitsPlatform API at https://api.corva.ai
Read or write permitted time, depth, engineering, or reference datasetsData API at https://data.corva.ai
Receive new records in a Dev Center frontend appData API for initial data, then socketClient for updates
Call either API from a Dev Center frontend appcorvaAPI or corvaDataAPI from @corva/ui

See Choose the Right API for a fuller comparison.

Typical request flow​

  1. Choose an API key or Bearer token and store secrets outside your source code.
  2. Query the Platform API for the well or other asset you need. For wells, choose /v2/wells or /v2/assets based on the workflow.
  3. Read attributes.asset_id from a /v2/wells response, or the top-level id from a /v2/assets response.
  4. Pass that asset_id in a Data API dataset query.
  5. Page through additional records or subscribe to new data when required.
New to the APIs?

Follow the Quickstart. It uses small responses and copyable examples so you can verify access before building a larger integration.

Endpoint references​

These maintained references preserve the parameter tables, examples, and representative responses needed for common customer workflows:

The Swagger interfaces remain available as supplemental interactive explorers, but generated parameter descriptions and examples may lag behind the services.