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

ShieldLabs Management API

Profile and balance on api.shieldlabs.ai. Authenticated with Secret Key headers (`Authorization: Bearer` plus `X-Shield-Domain`). Its `GET /v1/history` path returns a PascalCase JSON array and is DEPRECATED with a Sunset of 2027-01-01 — use the History API instead. Legacy path authentication carries the same sunset date.

ShieldLabs Management API is one of 3 APIs that ShieldLabs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Management API. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and 1 JSON Schema.

This API exposes 2 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.2.

Requests are made against 2 base URLs: https://account.shieldlabs.ai/api, https://api.shieldlabs.ai.

2 operations 2 paths 4 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2
Base URL
https://api.shieldlabs.ai
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

ShieldLabs Management API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (PrivateApiKey). It accepts HTTP bearer tokens (SecretKeyHeader).

  • PrivateApiKey — Private API Key from the dashboard API tab (sec…).
  • SecretKeyHeader — Secret Key plus X-Shield-Domain header with your registered domain.

Paths & Operations 2

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

management-api 2

Profile and balance on api.shieldlabs.ai. Authenticated with Secret Key headers. GET /v1/history is deprecated; use History API.

GET
/v1/profile
Get domain profile
getProfileV1 → 200401
GET
/v1/history/{type}/{value}deprecated
Search history by identifier (deprecated)
searchHistoryV1 3 params → 200400401404429503

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Snapshot (16 properties), Profile (5 properties), ScoreDetail (2 properties), Error (1 property). Each schema is shown below with its type and property counts.

Error
object
1 property
Snapshot
object
Deprecated Management History array element (PascalCase). Prefer History API snakecase rows.
16 properties
Profile
object
5 properties
ScoreDetail
object
Signal row on Management API Snapshot.Details (PascalCase). Not used in webhooks.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

shieldlabs-management-api-api-openapi.yml Raw ↑

Other APIs ShieldLabs publishes across the network.

ShieldLabs History API
ShieldLabs ShieldLabs API
Where this information came from

This is an independent, third-party profile of ShieldLabs Management 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.