Skip to main content

Drilling Reports

Reference payloads for segment: drilling. Each example shows the full request envelope. Include the well identifiers your system has in every report.

Daily Drilling Report — ddr​

One payload per daily report. Writes daily and cumulative cost (data.costs) and the 24-hour summary and forecast (data.operation-summaries). The report end time is the key: resending the same report end time updates that day.

{
"segment": "drilling",
"report_type": "ddr",
"data": {
"idwell": "A1B2C3D4E5F60718293A4B5C6D7E8F90",
"wellida": "42123456780000",
"wellname": "Example Ranch 12-1 1H",
"wellbore_name": "Original Hole",
"rig_number": "Example Rig 101",
"dttmstart": "2026-10-25T06:00:00",
"dttmend": "2026-10-26T06:00:00",
"summaryops": "Drilled 8-3/4in lateral from 14,210 ft to 15,480 ft. Circulated and surveyed.",
"plannextrptops": "Continue drilling lateral to TD.",
"daily_cost": 84250.00,
"cumulative_cost": 2310400.00
}
}
FieldUsed for
dttmendReport date and update key (required)
summaryops24-hour operations summary
plannextrptopsNext 24-hour forecast
daily_cost, cumulative_costDaily and cumulative field cost

Time log with NPT — timelog​

One payload per daily report, containing every time log entry for that report. Fusion writes the entries to the time log and also writes entries flagged is_npt: true as NPT events. Resend the full day to update it.

{
"segment": "drilling",
"report_type": "timelog",
"data": {
"idwell": "A1B2C3D4E5F60718293A4B5C6D7E8F90",
"wellida": "42123456780000",
"wellname": "Example Ranch 12-1 1H",
"wellbore_name": "Original Hole",
"job_idrec": "5F2E8A10C3B94D7E9A61B2C3D4E5F607",
"timelog": [
{
"idrec": "0C1D2E3F405162738495A6B7C8D9E0F1",
"dttmstart": "2026-10-25T06:00:00",
"dttmend": "2026-10-25T11:30:00",
"duration": 5.5,
"code1": "DRILL",
"code2": "ROTATE",
"code3": "LATERAL",
"com": "Drill 8-3/4in lateral 14,210 ft - 14,790 ft.",
"is_npt": false
},
{
"idrec": "1D2E3F405162738495A6B7C8D9E0F1A2",
"dttmstart": "2026-10-25T11:30:00",
"dttmend": "2026-10-25T13:00:00",
"duration": 1.5,
"code1": "REPAIR",
"code2": "TOPDRIVE",
"code3": "IBOP",
"com": "Replace leaking IBOP valve.",
"is_npt": true
}
]
}
}
FieldUsed for
timelog[]One object per time log entry
dttmstart, dttmend, duration (hours)Entry start, end and duration
code1–code3Activity codes (Corva maps your code list to Corva activities during onboarding)
comComment
is_npttrue also writes the entry as an NPT event

The completions time log uses the same pattern.

NPT event — npt_drilling​

Use this when your system stores NPT or problem events separately from the time log. Send one event per payload. idrec is the update key.

{
"segment": "drilling",
"report_type": "npt_drilling",
"data": {
"idrec": "C7838CFFA4E74BB8AA8FB6693035245D",
"idwell": "A1B2C3D4E5F60718293A4B5C6D7E8F90",
"wellname": "Example Ranch 12-1 1H",
"wellbore_name": "Original Hole",
"dttmstart": "2026-10-25T11:30:00",
"dttmend": "2026-10-25T13:00:00",
"typ": "Surface Equipment - Rig",
"typdetail": "Top Drive",
"des": "IBOP valve",
"accountablepty": "Example Drilling Contractor",
"com": "Changed out IBOP on top drive due to leak.",
"depthstart": 14790,
"depthend": 14790
}
}

dttmstart and dttmend are required. Fusion calculates the duration.

Bit run and dull grade — drillbit​

One payload per bit run.

{
"segment": "drilling",
"report_type": "drillbit",
"data": {
"idwell": "A1B2C3D4E5F60718293A4B5C6D7E8F90",
"idrec": "924E8E2A403B489EB8DD0ADA0802513D",
"apinumber": "42123456780000",
"wellname": "Example Ranch 12-1 1H",
"wellbore_name": "Original Hole",
"depthdrilledstart": 6081.0,
"make": "Example Bits Co",
"model": "XD506",
"sn": "5326259",
"wearinner": 1,
"wearouter": 2,
"weardull": "CT",
"wearloc": "S",
"wearbearing": "X",
"weargauge": "I",
"wearother": "NO",
"wearpulled": "TD"
}
}

The wear* fields are the IADC dull grade (inner, outer, dull characteristic, location, bearing, gauge, other, reason pulled). depthdrilledstart identifies the run on the well.

Mud check — mud_report​

The reference shape follows WITSML fluidsReport naming in JSON, with {"value", "uom"} measurements. Each object in fluids[] becomes one mud check in Corva, keyed by its dTim.

{
"segment": "drilling",
"report_type": "mud_report",
"data": {
"nameWell": "Example Ranch 12-1 1H",
"nameWellbore": "Original Hole",
"dTim": "2026-10-25T23:00:00",
"fluids": [
{
"dTim": "2026-10-25T18:00:00",
"type": "Oil-based",
"locationSample": "Flow Line",
"md": { "value": 15100, "uom": "ft" },
"density": { "value": 10.2, "uom": "lbm/galUS" },
"visFunnel": { "value": 52, "uom": "s/qt" },
"pv": { "value": 18, "uom": "cP" },
"yp": { "value": 12, "uom": "lbf/100ft2" },
"gel10Sec": { "value": 8, "uom": "lbf/100ft2" },
"gel10Min": { "value": 12, "uom": "lbf/100ft2" },
"electStab": { "value": 650, "uom": "V" },
"oilPc": { "value": 68, "uom": "%" },
"waterPc": { "value": 17, "uom": "%" },
"solidsPc": { "value": 15, "uom": "%" },
"rheometer": { "vis600Rpm": 48, "vis300Rpm": 30, "vis200Rpm": 24, "vis100Rpm": 17, "vis6Rpm": 8, "vis3Rpm": 7 }
}
]
}
}

Required in each fluid: density, md, pv and yp. A check without them fails validation.

Mud inventory, volumes and pumps (mud_inventory) follow the same WITSML naming (mudVolume, mudInventory[], pumps[]). Ask Corva for that example.

Directional survey — survey​

Send the full survey (all stations to date) in each payload.

{
"segment": "drilling",
"report_type": "survey",
"data": {
"wellname": "Example Ranch 12-1 1H",
"wellbore_name": "Original Hole",
"stations": [
{ "measured_depth": 0, "inclination": 0, "azimuth": 0, "vertical_depth": 0, "northings": 0, "eastings": 0 },
{ "measured_depth": 118.44, "inclination": 0.61, "azimuth": 245.74, "vertical_depth": 118.44, "northings": -0.26, "eastings": -0.57 }
]
}
}

measured_depth, inclination and azimuth are required for every station. Corva calculates the other values if you leave them out.

Surveys are not tie-in adjusted

Fusion keeps the survey section already in Corva and adds the stations you send.

Other drilling report types​

Fusion also accepts casing, well plans, BHA, formation tops, well sections, alerts and more. See Report Types for the full list, and ask your Corva contact for the reference payload before you build any of them.