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

Netter ontology-records API

The ontology-records API from Netter — 4 operation(s) for ontology-records.

Netter ontology-records API is one of 44 APIs that Netter publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://api.netter.ai.

4 operations 4 paths 4 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.netter.ai
Resource Areas
1

Paths & Operations 4

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

ontology-records 4
GET
/api/v1/ontology/entities/{entity_id}/records
List Records
list_records_api_v1_ontology_entities__entity_id__records_get 6 params → 200422
GET
/api/v1/ontology/entities/{from_entity_id}/unmatched/{to_entity_id}
List Unmatched Records
list_unmatched_records_api_v1_ontology_entities__from_entity_id__unmatched__to_entity_id__get 5 params → 200422
GET
/api/v1/ontology/entities/{from_entity_id}/matched/{to_entity_id}
List Matched Records
list_matched_records_api_v1_ontology_entities__from_entity_id__matched__to_entity_id__get 4 params → 200422
GET
/api/v1/ontology/entities/{entity_id}/records/{record_key}/related
Get Record Related
get_record_related_api_v1_ontology_entities__entity_id__records__record_key__related_get 2 params → 200422

Schemas 4

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

HTTPValidationError
object
1 property
ValidationError
object
5 properties 3 required
RecordRelatedResponse
object
Response for GET /ontology/entities/{id}/records/{key}/related.
4 properties 4 required
RelatedRecordSet
object
Related records for one entity.
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

netter-ontology-records-api-openapi.yml Raw ↑

Other APIs Netter publishes across the network.

Netter actions API
Netter api-keys API
Netter app-chat API
Netter apps API
Netter apps-query API
Netter assistant API
Netter attributes API
Netter automations API
Netter chats API
Netter companies API
Netter dashboard-chat API
Netter dashboard-data API
Where this information came from

This is an independent, third-party profile of Netter ontology-records 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.