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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Indykite

Indykite Entity Matching API

Entity Matching Pipeline configuration

Documentation Provider Profile APIs.io OpenAPI GitHub

Indykite Entity Matching API is one of 20 APIs that Indykite publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Entity Matching. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 8 operations across 5 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against 2 base URLs: https://eu.api.indykite.com/configs/v1, https://us.api.indykite.com/configs/v1.

8 operations 5 paths 17 schemas 1 DELETE4 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://us.api.indykite.com
Authentication
HTTP Bearer, HTTP Bearer, API Key
License
Apache 2.0
Resource Areas
1

Authentication & Security 3

Indykite Entity Matching API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerToken). It accepts HTTP bearer tokens (bearerAuth). An API key is passed in the header as X-IK-ClientKey (APIKey). By default, every request must be authenticated.

  • BearerToken — Bearer token generated from Service Account credentials.
  • bearerAuth — Bearer token - the value of the Authorization header (without Bearer), e.g. "superSecretToken".
  • APIKey — The value of the App Agent credential header must be passed as is, without any prefix.

Paths & Operations 8

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

Entity Matching 8

Entity Matching Pipeline configuration

GET
/entity-matching-pipelines
List Entity Matching Pipelines
listEntityMatchingPipelines 3 params → 200400401403404422500
POST
/entity-matching-pipelines
Create Entity Matching Pipeline
createEntityMatchingPipeline body → 201400401403404422500
DELETE
/entity-matching-pipelines/{id}
Delete Entity Matching Pipeline
deleteEntityMatchingPipeline 2 params → 200400401403404422500
GET
/entity-matching-pipelines/{id}
Read Entity Matching Pipeline
getEntityMatchingPipeline 3 params → 200400401403404422500
PUT
/entity-matching-pipelines/{id}
Update Entity Matching Pipeline
updateEntityMatchingPipeline 2 params body → 200400401403404422500
GET
/pipelines/{id}/property-mappings
EntityMatching read suggested property mapping endpoint
getPipelinesPropertyMapping 1 param → 200202400404409422500
POST
/pipelines/{id}/runs
EntityMatching run endpoint
createPipelinesRun 1 param body → 202400404422500
GET
/pipelines/{id}/status
EntityMatching read pipeline status endpoint
getPipelinesByIdStatus 1 param → 200400404409422500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are httpproxy.readEntityMatchingPipelineResponse (22 properties), httpproxy.createEntityMatchingPipelineRequest (7 properties), api.SuggestedPropertyMapping (5 properties), httpproxy.entityMatchingPipelinePropertyMapping (5 properties). Each schema is shown below with its type and property counts.

restapi.ErrorResponse
object
1 property
httpproxy.updateEntityMatchingPipelineRequest
object
4 properties
httpproxy.createEntityMatchingPipelineRequest
object
7 properties 4 required
restapi.DetailedError
object
2 properties
httpproxy.listConfigResponse-httpproxy_readEntityMatchingPipelineResponse
object
1 property
httpproxy.updateConfigResponse
object
5 properties
httpproxy.createConfigResponse
object
5 properties
httpproxy.entityMatchingPipelineNodeFilter
object
2 properties 2 required
httpproxy.entityMatchingPipelinePropertyMapping
object
5 properties
httpproxy.deleteConfigResponse
object
1 property
httpproxy.readEntityMatchingPipelineResponse
object
22 properties
api.SuggestedPropertyMapping
object
5 properties
api.CustomPropertyMapping
object
2 properties 2 required
api.ReadSuggestedPropertyMappingResponse
object
2 properties
api.RunEntityMatchingPipelineResponse
object
3 properties
api.RunEntityMatchingRequest
object
2 properties 1 required
restapi.DetailedMessageResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

indykite-entity-matching-api-openapi.yml Raw ↑

Other APIs Indykite publishes across the network.

Indykite Application Agent Credentials API
AE Profile APIs.io
Indykite Application Agents API
AE Profile APIs.io
Indykite Applications API
AE Profile APIs.io
Indykite Authorization Policies API
AE Profile APIs.io
Indykite Capture API
AE Profile APIs.io
Indykite ContX IQ API
AE Profile APIs.io
Indykite Deprecated API
AE Profile APIs.io
Indykite Event Sinks API
AE Profile APIs.io
Indykite External Data Resolver API
AE Profile APIs.io
Indykite Knowledge Queries API
AE Profile APIs.io
Indykite MCP Servers API
AE Profile APIs.io
Indykite Organizations API
AE Profile APIs.io
#Entity Matching
← Back to I APIs
API Details
ID
indykite:indykite-entity-matching-api
Base URL
https://us.api.indykite.com
Docs
https://openapi.indykite.com
Provider
Indykite
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=indykite-entity-matching-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/indykite-entity-matching-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Indykite Entity Matching 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.