Skip to content
English
  • There are no suggestions because the search field is empty.

API v3 Release

We’re excited to announce the release of API Version 3 (v3), which makes integrations simpler, faster, and future-ready.

What's New

With the release of API v3, the API now includes support for ML products in addition to Datarock Core. V3 also introduces artefact-level access, giving users more precise control over the data they retrieve.
In addition, a structured product taxonomy has been implemented to improve data organisation and make it easier to understand product outputs.


Improvements

  • Multi-Tenancy Support
    The API now delivers products from both Datarock Core and ML (Nexus), giving you unified programmatic access to the full product portfolio.

  • Artefact-Level Access
    Instead of receiving grouped artefacts, you can now request data at the individual artefact level, allowing for more precise and efficient system-to-system integrations.

  • Structured Product Taxonomy
    API responses now follow a clear taxonomy that makes product data easier to understand and organise. This includes:

    • Product categories.

    • Product names.

    • Product descriptions.

    • Hierarchical organisation of artefacts within responses.

 
 

Benefits of API v3

  • Simplified Integration
    Access all product types through a single API endpoint.

  • Improved Precision
    Retrieve data at the artefact level, reducing bandwidth usage and processing overhead for automated systems.

  • Better Organisation
    Use the structured taxonomy to programmatically identify and categorise product outputs.

  • Future-Ready
    Built on a foundation that supports expansion to additional tenancies and data types.

Getting started with API v3

Limitations

  • Integration Updates Required
    Existing API users will need to update their integration code to take advantage of artefact-level access and the new taxonomy features in v3.

  • Transition Period
    v2 will remain available for up to 6 months to support backward compatibility and migration. However, all new integrations should be built on v3 to access ML products and future enhancements.

Users of the API v2 will need to migrate their integrations to v3.