Skip to main content

Request Format

Every request has the same envelope. Only the contents of data change from one report type to another.

{
"segment": "drilling",
"report_type": "ddr",
"data": { },
"historical": false,
"metadata": { "source": "my-pipeline-v1" }
}
FieldTypeRequiredDescription
segmentstringYesdrilling, completions or intervention. Use the segment of the Corva asset the data belongs to.
report_typestringYesThe report type key or one of its aliases. See Report Types.
dataobjectYesThe report itself. See the payload reference. Send one well per request.
historicalbooleanNoSet true for backfills of past data. Leave it out for live data.
metadataobjectNoFree-form information about the sender, such as pipeline name or version. Helpful for support.
create_new_assetbooleanNoOnly for the create_asset report type, when agreed with Corva.
referencebooleanNoOnly for reference data that does not belong to a single well, when agreed with Corva.
data.s3_pathsstring[]NoHTTPS pre-signed file URLs Fusion should download (for example PDFs to attach to the well). Fusion creates one report per URL and returns an array of report IDs.
company_idnumberNoIgnored. Your company comes from the API key.

Rules for data​

  • Well identification. Include at least one well identifier, and preferably more than one: API/UWI number, your own well ID (for example WellView idwell), well name, and wellbore name. See Well Identification.
  • Timestamps. Use ISO 8601 (2026-10-25T06:00:00) or yyyy-MM-dd HH:mm:ss. Timestamps without a UTC offset are read as the well's local time.
  • Stable record IDs. Give every record a stable unique ID (for example WellView idrec) that stays the same across resends. Fusion uses it to update the existing record instead of creating a duplicate.
  • Units. Send values in the units your system stores them in and tell Corva which units they are. For measurements that carry units, the {"value": …, "uom": "…"} pattern (as in the mud check example) lets Fusion convert per value.
  • Nulls. Send null or leave out fields you don't have. Don't send placeholder strings such as "N/A" in numeric fields.
  • Size. The maximum request size is 50 MB. Keep each request well below it by splitting large histories by day or by well. Oversized requests are rejected with a 500 (see HTTP responses).