how to capture APIs?

We’re expanding our Collibra Asset Model, and we want to capture APIs. There isn’t a standard, OOTB asset class for them. But, I know we cannot be the only ones capturing them (and the models that support them). It seems like there are some challenges to with the typical ‘physical’ assets which always breakdown into schema, table, column – esp since our REST APIs are all JSON and the table/column isn’t convenient. (And we’d like to leverage swagger or similar for upload).

Any ideas? Or standard tools in the marketplace I might have missed?

dianereynolds

Posted 5 years ago · Edited 1 year ago·Last reply 5 years ago

3 comments

noor

·5 years ago · Edited

Looks like there is tool in marketplace too. atleast the approach can be looked at here -

Lorang API Governance (APIGov) - Collibra Marketplace

Govern and secure APIs to ensure that they are visible, available, documented, standardized, classified & enriched with business taxonomies.

arthurburkhardt

·5 years ago · Edited

In addition, we had two great session (in french) during the last France user meetup from CMA-CGM and ADEO.
Both of those sessions presented ways to govern APIs: https://datacitizens.collibra.com/forum/t/data-citizens-france/430/4

pmahend3

·5 years ago · Edited

Hi Diane,

Unfortunately, there is no OOTB metamodel to represent APIs and I’ve seen very creative ways other Collibra users have come up with to solve this problem. Check this thread out for some ideas - https://datacitizens.collibra.com/forum/t/how-to-represent-apis-in-collibra/341/6