Fusion API
Fusion is Corva's data ingestion service for well reports. Your system sends a report to the Fusion API as JSON (a daily drilling report, a time log, a mud check, a frac stage, and so on). Fusion then:
- matches the report to the right well in Corva,
- maps your fields to Corva's data model, and
- writes the result to the Corva datasets that power Corva's apps.
You keep your own field names. Corva configures the mapping once during onboarding. If your payload matches one of the shapes in the payload reference, onboarding usually needs no custom mapping at all.
Start hereSend your first reportPost a report and check that it reached Corva.Request formatBuild the request envelopeLearn the fields every report shares and the rules for its data.Payload referenceShape your report dataSee reference payloads for drilling and completions report types.ProcessingTrack what happenedCheck report status, handle errors, and resend or backfill data.
Fusion or the Data API?
Fusion and the Corva API are separate services with separate keys.
| You want to… | Use |
|---|---|
| Send reports from WellView or another system of record into Corva's own datasets | Fusion API |
| Find wells and read operational records stored in Corva | Platform API and Data API |
| Write records to a custom dataset your company owns | Data API |
Typical integration flow
- Work through the onboarding checklist with Corva. Corva sets up your report types and mappings and issues a Fusion API key.
- Build each report in the request envelope, using the payload reference for the
dataobject. POSTthe report to the URL for your Corva environment and keep the returned report ID.- Check the report status to confirm the data reached Corva.
Include the report ID in support requests
Every report you post gets a Fusion report ID. Include it whenever you contact your Corva integration contact or the Corva support portal about a report.