Endpoints and Authentication
Base URL per Corva environment
Use the URL for the Corva environment your wells live in. Every URL ends in /integration. Posting to the host root returns an error.
| Corva environment | POST URL |
|---|---|
| United States (app.corva.ai) | https://api.fusion.corva.ai/integration |
| Europe (app.eu.corva.ai) | https://api.eu.corva.ai/api/fusion/integration |
| Brazil (app.br.corva.ai) | https://api.br.corva.ai/api/fusion/integration |
| Saudi Arabia (app.ad.corva.ai) | https://api.ad.corva.ai/api/fusion/integration |
| Malaysia (app.my.corva.ai) | https://api.my.corva.ai/api/fusion/integration |
| UAE (app.uae.corva.ai) | https://api.uae.corva.ai/api/fusion/integration |
Each environment is separate: an API key issued for one environment does not work in another. Dedicated or customer-hosted deployments get their URL from your Corva integration contact. A test (QA) environment is available on request.
Routes
| Method | Path (append to the base URL) | Purpose |
|---|---|---|
| POST | /integration | Submit one report for processing |
| GET | /integration/report-status/{reportId} | Check the processing status of a report you submitted |
Example (US): GET https://api.fusion.corva.ai/integration/report-status/6a1f0c2e9b3d4e5f6a7b8c9d
Authentication
Corva issues each integration a Fusion API key. The key belongs to your company, so everything you post is assigned to your company automatically.
Send the raw key as the Authorization header value:
Authorization: YOUR_FUSION_API_KEY
Do not add a Bearer or API prefix. A Fusion API key is not a Corva Platform or Data API key, and the two are not interchangeable. See Authentication for the keys used by the Platform and Data APIs.
- Treat the key as a secret. Store it in a secrets manager and never put it in source control. If you think a key has been exposed, ask Corva to rotate it.
- Corva can issue more than one key per company, for example one per pipeline, so each one can be rotated on its own.