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...

how to capture APIs? | Use cases

how to capture APIs? | Use cases | Collibra Community