Sign Up Now: Type Curve 2.0 API preview

Uncategorized
1

Type Curve 2.0 API preview: test your own data against the V2 API before November 7

On Saturday, November 7, we convert every type curve from Type Curve 1.0 to Type Curve 2.0 and retire the V1 type-curve API routes. You can try the V2 API on your own data before then. Please read the three points below before you opt in.

Read this before you opt in

  • Opting in converts your Type Curve 1.0 data to Type Curve 2.0. We run the conversion for you on a tenant of your choice. It is a copy: your Type Curve 1.0 data is never changed.
  • Type Curve 1.0 stays the official, supported version until Saturday, November 7. Keep running production on the V1 API and the current application until then. The preview does not replace it.
  • Everything converted during the preview will be erased and migrated again on November 7. On cutover day, we reset the preview tenant and re-migrate it from Type Curve 1.0, like every other tenant. Anything you create or edit in Type Curve 2.0 on the preview tenant is discarded. Do not keep work there that you need to keep.

What you get

  • The V2 API turned on for your preview tenant: list, get, create, update, delete, fits, normalization, volumes, wells, and lookup tables.
  • The Type Curve 2.0 screens are enabled in the application for the same tenant, so you can review your converted data and the changes in the UI and the API.
  • Every type curve keeps its V1 ID, so IDs you store today keep working.
  • The pretesting/opt-in conversion is run when you ask, not on a schedule. If you want a fresh copy of your V1 data later, ask, and we will re-run it; a re-run refreshes the converted type curves, so edits you made to them are replaced. We confirm with you before any re-run.

Documentation

Good to know before you start

  • V2 base path is /v2/projects/{projectId}/type-curves. Fields that are not set are left out of responses, not returned as null.
  • GET /{id}/fits/daily and /fits/monthly are replaced by GET /{id}/volumes?resolution=daily|monthly. resolution is required.
  • Creating a type curve with fits is now two calls: POST the type curve, then PUT /{id}/fits. Updates use PATCH, not PUT.
  • GET /head and the V1 representative-wells route are removed. Wells are under /{id}/wells.
  • Normalized values will not match V1 exactly. Validate against the documented V2 behavior, not against V1 equality.
  • After November 7, the V1 type-curve routes return 410 Gone. Plan your own cutover so your production integration switches to V2 on or after November 7.
  • Use your existing API keys and the same API host. Only the preview tenant responds with V2 before November 7.
  • If you use our C# SDK, please update with the latest NuGet Gallery | ComboCurve.Api 1.47.1-prerelease

To opt in: Email support with the tenant you want to use. We convert it and turn on V2 (API and screens) within one to two business days. Questions are welcome in the Type Curve 2.0 forum topic.

1 Like
Type Curve 2.0