Quickstart
In this guide you will post one Daily Drilling Report to Fusion and check that it reached Corva. You need a Fusion API key from Corva. The examples use the United States environment; use the URL for your environment if your wells live elsewhere.
1. Store your Fusion API key
Set the key as an environment variable so it does not appear in your source code.
export FUSION_API_KEY='YOUR_FUSION_API_KEY'
Fusion expects the raw key as the Authorization header value:
Authorization: YOUR_FUSION_API_KEY
Do not add a Bearer or API prefix. This differs from the Platform and Data APIs, and a Corva Platform API key does not work with Fusion.
2. Post a report
Replace the well identifiers with ones for a well your company has in Corva.
curl -sS -X POST 'https://api.fusion.corva.ai/integration' \
-H 'Content-Type: application/json' \
-H "Authorization: <YOUR_FUSION_API_KEY>" \
-d '{
"segment": "drilling",
"report_type": "ddr",
"data": {
"...": "your report fields (See Payload Reference)"
}
}'
A 200 OK response contains the Fusion report ID, for example "6a1f0c2e9b3d4e5f6a7b8c9d". Keep it for the next step.
200 OK means Fusion accepted and queued the report. Parsing and validation problems never appear in the POST response, so always check the status.
3. Check the report status
curl -sS 'https://api.fusion.corva.ai/integration/report-status/6a1f0c2e9b3d4e5f6a7b8c9d' \
-H "Authorization: YOUR_FUSION_API_KEY"
Most reports finish within seconds to a few minutes. A success status means the data is in Corva:
{
"status": "success",
"logs": [
{ "date": 1793116800, "step": "integration", "status": "ok" },
{ "date": 1793116801, "step": "report-type-identification", "status": "ok" },
{ "date": 1793116801, "step": "asset-identification", "status": "ok" },
{ "date": 1793116803, "step": "production", "status": "ok" }
]
}
If the status is fail, see Troubleshooting.
Next steps
- Learn the full request format and how Fusion identifies wells.
- Find the reference payload for your report type under drilling reports or completions reports.
- Read how status, errors, updates and backfills work before going live.