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

Anomalo API Keys API

The API Keys API from Anomalo — 2 operation(s) for api keys.

Anomalo API Keys API is one of 19 APIs that Anomalo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include APIKeys. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and API documentation.

This API exposes 3 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://{instance}/api/public/v1.

3 operations 2 paths 1 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://app.anomalo.com/api/public/v1
Authentication
API Key, HTTP Bearer
Contact
License
Apache-2.0
Resource Areas
1

Authentication & Security 2

Anomalo API Keys API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Anomalo-Token (AnomaloToken). It accepts HTTP bearer tokens (BearerToken). By default, every request must be authenticated.

  • AnomaloToken — Anomalo API secret token. The first-party client sends it as X-Anomalo-Token by default (legacyauth=True), read from the ANOMALOAPISECRETTOKEN environment vari…
  • BearerToken — Anomalo API secret token sent as Authorization: Bearer . Selected in the first-party client with legacyauth=False.

Paths & Operations 3

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

API Keys 3
GET
/api-keys
List api keys for current user
list_api_keys_for_current_user 2 params → 200400401403404500
POST
/api-keys
Create api key for current user
create_api_key_for_current_user body → 200400401403404500
DELETE
/api-keys/{api_key_id}
Revoke api key for current user
revoke_api_key_for_current_user 1 param → 200400401403404500

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

Error
object
Error body. The first-party client raises BadRequestException for 4xx and RuntimeError for 5xx, carrying the raw response text; Anomalo does not publish a docu…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anomalo-api-keys-api-openapi.yml Raw ↑

Other APIs Anomalo publishes across the network.

Anomalo MCP Server
Anomalo Access Groups API
Anomalo Check Runs API
Anomalo Checks API
Anomalo Document Collections API
Anomalo Documents API
Anomalo Exports API
Anomalo Issues API
Anomalo Labels API
Anomalo Lineage API
Anomalo Notification Channels API
Anomalo Organizations API
Where this information came from

This is an independent, third-party profile of Anomalo API Keys 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.