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

Ntropy Labels API

The Labels API from Ntropy — 2 operation(s) for labels.

Ntropy Labels API is one of 16 APIs that Ntropy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://api.ntropy.com.

4 operations 2 paths 5 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.ntropy.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Ntropy Labels API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Api-Key (APIKeyHeader).

Paths & Operations 4

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

Labels 4
GET
/v2/labels/hierarchy/{account_holder_type}
Get the hierarchy of Ntropy labels
get_labels_hierarchy_v2_labels_hierarchy__account_holder_type__get 1 param → 200400422
POST
/v2/labels/hierarchy/custom/{account_holder_type}
Upload a custom label hierarchy
custom_hierarchy_post_v2_labels_hierarchy_custom__account_holder_type__post 1 param body → 200400422
GET
/v2/labels/hierarchy/custom/{account_holder_type}
Get a custom label hierarchy
custom_hierarchy_get_v2_labels_hierarchy_custom__account_holder_type__get 1 param → 200400422
DELETE
/v2/labels/hierarchy/custom/{account_holder_type}
Delete a custom label hierarchy
delete_custom_hierarchy_v2_labels_hierarchy_custom__account_holder_type__delete 1 param → 200422

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ValidationError (3 properties), LlmHierarchy (2 properties), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.

LabelsHierarchy
object
ValidationError
object
3 properties 3 required
LlmHierarchy
object
2 properties 2 required
HTTPValidationError
object
1 property
ntropy_core__db__account_holder_type__AccountHolderType
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ntropy-labels-api-openapi.yml Raw ↑

Other APIs Ntropy publishes across the network.

Ntropy Account Holder API
Ntropy accountHolders API
Ntropy Bank statements API
Ntropy bankStatements API
Ntropy batches API
Ntropy categories API
Ntropy Enrichment API
Ntropy entities API
Ntropy Misc API
Ntropy personalization API
Ntropy recurrence API
Ntropy Reporting API
Where this information came from

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