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

Dust Identity Slices API

The Slices API from Dust Identity — 3 operation(s) for slices.

Dust Identity Slices API is one of 24 APIs that Dust Identity publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Slices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 3 operations across 3 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 2026.7.4.

Requests are made against a single base URL, https://apid.dustid.io.

3 operations 3 paths 10 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026.7.4
Base URL
https://apid.dustid.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Dust Identity Slices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

  • Bearer — JWT issued by the DUST auth service. Obtain one by exchanging a Service Account API key (GET /api/auth/token with the key header) or via the OAuth2 clientcrede…

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Slices 3
POST
/api/v1/slices
Slice a thread (same-team derivation)
slice.create body → 200400401404
POST
/api/v1/slices/batch
Slice a thread into many derived threads in one operation
slice.create_many body → 200400401404
GET
/api/v1/slices/{slice_id}
Get a Slice with its Fabric Links
slice.get 1 param → 200401404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are FabricStateChangeReason (10 properties), CreateManySliceRequest (9 properties), CreateSliceRequest (9 properties), SliceFieldValue (4 properties). Each schema is shown below with its type and property counts.

SliceLink
object
4 properties 4 required
SliceTargetInput
object
3 properties
SliceResult
object
3 properties 3 required
CreateSliceRequest
object
9 properties 1 required
CreateManySliceRequest
object
9 properties 2 required
FabricStateChangeReason
object
10 properties 7 required
SliceGetResponse
object
2 properties 2 required
SliceCreateResponse
object
4 properties 4 required
SliceCreateManyResponse
object
2 properties 2 required
SliceFieldValue
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dust-identity-slices-api-openapi.yml Raw ↑

Other APIs Dust Identity publishes across the network.

DUST AuthD
Dust Identity Auth API
Dust Identity Bundles API
Dust Identity Certificate Forms API
Dust Identity Certificates API
Dust Identity Connections API
Dust Identity Events API
Dust Identity Fabric API
Dust Identity Files API
Dust Identity Metrics API
Dust Identity Notifications API
Dust Identity Org Admin API
Where this information came from

This is an independent, third-party profile of Dust Identity Slices 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.