Skip to main content

Report Types

report_type takes the key or any alias listed. Some aliases are shared across segments (for example casing_tally), so always send the correct segment.

The Lands in column names the Corva dataset the report writes to. You can read those records back with the Data API.

SegmentKeyAlso acceptedLands in (Corva dataset)
drillingddrdwr, cost, costsdata.costs, data.operation-summaries
drillingtimelogdrilling_timelogdrilling.timelog.data (+ data.npt-events)
drillingnpt_drillingnpt, drilling_npt, npt_timelogdata.npt-events
drillingdrillbit—data.drillstring
drillingmud_reportmud, dmrdata.mud
drillingmud_inventory—drilling.mud-ops
drillingsurvey—data.actual_survey
drillingwell_plan—data.plan_survey
drillingbha—data.drillstring
drillingcasingcasing_tallydata.casing
drillingformationsformation_topdata.formations
drillingwell_sectionwell_sections, wellsectionwell sections / planned tasks
drillingalertalertsCorva alerts
drillingcreate_assetasset_create, assetcreates the well (by agreement)
completionspjrstage_summarycompletion.data.actual-stages
completionsdcrdwrcompletion.data.costs, completion.data.operation-summaries
completionstimelogcompletions_timelogcompletion.data.time-log.wv (+ completion.data.npt-events)
completionsnpt_completionnpt_completions, completions_nptcompletion.data.npt-events
completionscasing_tallycompletions_casing_tallycompletion.casing-tally
interventiontimelog_intervention—interventions.timelog.data
interventionnpt_intervention—interventions.data.npt-events
interventionddr_intervention—intervention daily report

Fusion also accepts cement, consumables and other report types not listed here. For any report type without a linked reference payload, ask your Corva contact for the example before you build it.