Type Curve 2.0 Cutover
Updated API documentation now available · Target cutover 7 November 2026
This follows up on our previous announcement about the Type Curve 2.0 migration. The target cutover date remains 7 November 2026, and the full V2 endpoint documentation is now published and available for your teams to build against.
Start here: Type Curve 2.0 Migration Guide
The online documentation is now the authoritative reference for this migration. It supersedes the migration guide distributed in August, which has since been extended in several areas. Please direct your engineering teams there rather than to the earlier document.
Two sections are directly relevant:
· Type Curve 2.0 Migration Guide — V1-to-V2 endpoint mapping, field renames and relocations, and the behavioral differences to expect
· Type Curves V2 (Preview) — the complete endpoint reference, covering type curves, fits, volumes, wells, normalization, and lookup tables
The V2 endpoints are documented ahead of the switch-over and do not respond until 7 November 2026. They are published now so your teams can complete implementation and review before the cutover weekend.
What happens at cutover
Data migration takes place over the cutover weekend. All existing Type Curve data is converted automatically to the Type Curve 2.0 schema — you do not need to recreate any records.
Type Curve V1 endpoints stop responding on 7 November 2026 and return 410 Gone. This is a one-way transition.
Only type curves and lookup tables are affected. Wells, forecasts, econ models, scenarios, productions, directional surveys, exports, and tags are unchanged.
If you consume Type Curve data through the API
Your existing data will be migrated, but several read and write operations move to new routes and revised contracts. This is an integration migration, not a base-path change.
The areas that most commonly require code changes:
· Fit data is no longer embedded on the type curve and is retrieved from a dedicated fits endpoint
· Type curve creation and fit writes are separate operations
· Collection updates use PATCH merge semantics and match on id rather than name
· Daily and monthly volume reads consolidate into a single endpoint with a required resolution parameter
· Several fit fields are renamed, relocated to the phase fit, or removed and rejected on write
· Absent fields are omitted from responses rather than returned as null
The migration guide documents each of these with the corresponding V1 and V2 payloads. We recommend working through the readiness checklist it provides and completing integration testing well ahead of the cutover weekend.
If you consume Type Curve data through SYNC
Your Type Curve data converts automatically as part of the migration, and the Snowflake and Databricks views will reflect the new Type Curve 2.0 schemas following the cutover.
Because the shape of that data changes, downstream ingestion, mapping, and validation logic will need to accommodate the new structure. Please engage your ComboCurve integrations contact to review your specific SYNC configuration and plan the downstream updates. We would rather work through this with you directly than have you infer the impact from the API documentation, which describes the REST contract rather than your warehouse views.
Documentation is being updated continuously
Several areas of the Type Curve 2.0 contract have been finalized and published since our August communication, including normalization and lookup table rules. We are continuing to refine and expand the documentation as remaining details are confirmed.
Please check the documentation site periodically rather than working from a point-in-time copy. Where your integration depends on an area still marked as preview, we recommend isolating that logic behind an adapter so the final contract can be applied without reworking surrounding code.
What we recommend now
1. Review the migration guide with your integration owners and engineers
2. Inventory the Type Curve V1 routes your systems call today
3. Implement and test V2 reads and writes against the published contract
4. SYNC customers: contact your integrations team to plan downstream changes
5. Re-check the documentation as the cutover approaches