Aggregate artifacts of a kind
As POST /aggregate, narrowed to one registered kind — and the kind is validated, so an unregistered or retired kind is a 404 rather than an empty result.
A kind's own properties are not dimensions or measures here, and that is the contract rather than a gap: a kind declares its properties at registration without declaring which of them are queryable, so the grammar has no name to validate against. Only the shared artifact fields group here, exactly as on POST /aggregate.
Request
- Base URL: https://api.atlan.com (the document declares no server; this is the origin it was published from)
- URL: https://api.atlan.com/registry/v1/aggregate/{artifact_kind}
- Auth: HTTP bearer
Path parameters
Registered kind (file, skill, …)
Headers
Codings applied to the request body, outermost last. Send base64, or gzip, base64 to compress first; the body is decoded before it is read and Content-Type still names the inner media type. Omit for an unencoded body.
Request body
Response
OK
Changes
No recorded changes to this operation across all 1 revision of this API.