How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Aserto directory API

The directory API from Aserto — 14 operation(s) for directory.

Aserto directory API is one of 8 APIs that Aserto publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Directory. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 18 operations across 14 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version version not set.

Requests are made against a single base URL, https://authorizer.prod.aserto.com.

18 operations 14 paths 32 schemas 4 DELETE7 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
version not set
Base URL
https://authorizer.prod.aserto.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Aserto directory API declares 2 security schemes for authenticating requests. An API key is passed in the header as authorization (AuthorizerAPIKey). An API key is passed in the header as aserto-tenant-id (TenantID). By default, every request must be authenticated.

Paths & Operations 18

Across 14 paths, the API surfaces 18 operations — 4 DELETE, 7 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

directory 18
POST
/api/v3/directory/assertion
Set assertion
directory.assertion.v3.assertion.set body → 200default
DELETE
/api/v3/directory/assertion/{id}
Delete assertion
directory.assertion.v3.assertion.delete 1 param → 200default
GET
/api/v3/directory/assertion/{id}
Get assertion instance
directory.assertion.v3.assertion.get 1 param → 200default
GET
/api/v3/directory/assertions
List assertions
directory.assertion.v3.assertions.list 2 params → 200default
POST
/api/v3/directory/check
Check
directory.reader.v3.check body → 200default
POST
/api/v3/directory/check/permissiondeprecated
Check permission
directory.reader.v3.check.permission body → 200default
POST
/api/v3/directory/check/relationdeprecated
Check relation
directory.reader.v3.check.relation body → 200default
POST
/api/v3/directory/checks
Checks
directory.reader.v3.checks body → 200default
GET
/api/v3/directory/graph/{object_type}/{relation}/{subject_type}
Get graph
directory.reader.v3.graph 8 params → 200default
DELETE
/api/v3/directory/manifest
Delete manifest
directory.model.v3.manifest.delete 1 param → 200default
POST
/api/v3/directory/object
Set object
directory.writer.v3.object.set body → 200default
DELETE
/api/v3/directory/object/{object_type}/{object_id}
Delete object
directory.writer.v3.object.delete 3 params → 200default
GET
/api/v3/directory/object/{object_type}/{object_id}
Get object instance
directory.reader.v3.object.get 5 params → 200304default
GET
/api/v3/directory/objects
List object instances
directory.reader.v3.objects.list 3 params → 200default
DELETE
/api/v3/directory/relation
Delete relation
directory.writer.v3.relation.delete 6 params → 200default
GET
/api/v3/directory/relation
Get relation instance
directory.reader.v3.relation.get 7 params → 200304default
POST
/api/v3/directory/relation
Set relation
directory.writer.v3.relation.set body → 200default
GET
/api/v3/directory/relations
List relations instances
directory.reader.v3.relations.list 10 params → 200default

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are v3Relation (9 properties), v3Object (7 properties), v3Assert (6 properties), v3CheckRequest (6 properties). Each schema is shown below with its type and property counts.

v3GetObjectsResponse
object
2 properties
v3CheckRelationResponse
object
2 properties
v3CheckPermissionRequest
object
6 properties 5 required
v3ChecksResponse
object
1 property
rpcStatus
object
3 properties
v3CheckRelationRequest
object
6 properties 5 required
v3SetRelationRequest
object
1 property 1 required
v3DeleteAssertionResponse
object
1 property
v3GetGraphResponse
object
3 properties
v3CheckResponse
object
3 properties
v3Relation
object
9 properties 5 required
v3SetRelationResponse
object
1 property
v3Assert
object
6 properties 1 required
v3CheckPermissionResponse
object
2 properties
v3ObjectIdentifier
object
2 properties 2 required
v3SetObjectResponse
object
1 property
v3DeleteRelationResponse
object
1 property
v3DeleteManifestResponse
object
1 property
v3SetAssertionRequest
object
1 property 1 required
v3GetRelationResponse
object
2 properties
v3Object
object
7 properties 2 required
v3CheckRequest
object
6 properties 5 required
v3SetAssertionResponse
object
1 property
v3GetObjectResponse
object
3 properties
v3GetAssertionResponse
object
1 property
v3PaginationResponse
object
1 property
v3ChecksRequest
object
2 properties
v3ListAssertionsResponse
object
2 properties
v3SetObjectRequest
object
1 property 1 required
v3GetRelationsResponse
object
3 properties
protobufAny
object
1 property
v3DeleteObjectResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aserto-directory-api-openapi.yml Raw ↑

Other APIs Aserto publishes across the network.

Aserto Decision Logs API
Aserto Control Plane API
Aserto Authorizer API
Aserto authzen API
Aserto decision_logs API
Aserto Info API
Aserto Policy API
Where this information came from

This is an independent, third-party profile of Aserto directory API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.