API v1 brings new features and better performance, improving how you interact with Cognite Data Fusion.
API v1 for Cognite Data Fusion (CDF) is now available. The release introduces new features, performance improvements, and other changes that will help companies in heavy-asset industries unlock the value of contextualized data for mobile workers, onshore experts, engineers, and operators.
“API v1 is a major step forward for Cognite Data Fusion,” said Maciej Mrowiec, Director of Product Management at Cognite. “With this release, CDF is more stable, more mature, and better equipped to meet the needs of enterprise customers.”
New features in API v1 include:
- External ID: You can now define a unique identifier for each data object in Cognite Data Fusion (CDF) as an optional extension to the existing ID field
- 3D API: You can now upload and process 3D models with the 3D API. At the moment, the API supports FBX files. We’ll add support for more file formats in the future
END-OF-LIFE DATES; UPGRADE NOW!
With API v1, we’re simplifying how users interact with CDF. All previous versions of the API -- 0.3, 0.4, 0.5, and 0.6 -- are scheduled to be removed over the next several months.
Beginning next year, there will only be one production version: v1.
If you’re already using versions 0.3, 0.4, 0.5, or 0.6, here’s what you need to know:
- v0.3 and v0.4 will be shut down on Sept. 10, 2019
- v0.5 and v0.6 will be shut down on Jan. 2, 2020
Regardless of which version you’re currently using, please plan to update as soon as possible. These API versions will not be available after the end-of-life dates listed above.
We’re standing by to help you make the switch. Contact us at firstname.lastname@example.org if you need assistance.
NEW, SIMPLIFIED VERSIONING SCHEME
Get used to the v1 name. With this release, we’re also changing our versioning scheme. Going forward, we will only use major version numbers. That means no minor revision numbers, no build numbers, and no need to worry about what’s new in v18.104.22.168-142.
We plan to stick with v1 for at least one year, but that doesn’t mean the API won’t be changing. In fact, we’ll continue to add new features to v1 as soon as they are ready. Only at the point where we need to change or break existing functionality will we release v2.
That means API v1 will get more powerful and feature-rich as we continue development. And if you simply aren’t interested in a new feature, you aren’t affected whatsoever.
We can’t wait to see what you’ll build.