Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kintsugi Nexus API

Physical and economic nexus tracking.

Kintsugi Nexus API is one of 9 APIs that Kintsugi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 5 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

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

5 operations 3 paths 2 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.trykintsugi.com/v1
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Kintsugi Nexus API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). An API key is passed in the header as x-organization-id (OrganizationId). By default, every request must be authenticated.

  • ApiKeyAuth — API key generated in the Kintsugi dashboard.
  • OrganizationId — Identifier of the organization the request acts on behalf of.

Paths & Operations 5

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

Nexus 5

Physical and economic nexus tracking.

GET
/nexus
Get nexus status for the organization.
getNexusForOrg → 200
POST
/nexus/physical
Create a physical nexus.
createPhysicalNexus body → 201
GET
/nexus/physical
List physical nexus entries.
getPhysicalNexus → 200
PATCH
/nexus/physical/{id}
Update a physical nexus.
updatePhysicalNexus 1 param body → 200
DELETE
/nexus/physical/{id}
Delete a physical nexus.
deletePhysicalNexus 1 param → 204

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Nexus (6 properties), PhysicalNexusRequest (4 properties). Each schema is shown below with its type and property counts.

PhysicalNexusRequest
object
4 properties 1 required
Nexus
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kintsugi-nexus-api-openapi.yml Raw ↑

Other APIs Kintsugi publishes across the network.

Kintsugi Address Validation API
Kintsugi Customers API
Kintsugi Exemptions API
Kintsugi Filings API
Kintsugi Products API
Kintsugi Registrations API
Kintsugi Tax Estimation API
Kintsugi Transactions API