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

Kintsugi Exemptions API

Customer tax exemptions and certificates.

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

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

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

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

5 operations 4 paths 6 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
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 Exemptions 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 4 paths, the API surfaces 5 operations — 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Exemptions 5

Customer tax exemptions and certificates.

POST
/exemptions
Create an exemption.
createExemption body → 201
GET
/exemptions
List exemptions.
getExemptions 2 params → 200
GET
/exemptions/{id}
Get an exemption by ID.
getExemptionById 1 param → 200404
POST
/exemptions/{id}/certificates
Upload an exemption certificate.
uploadExemptionCertificate 1 param body → 201
GET
/exemptions/{id}/attachments
Get attachments for an exemption.
getAttachmentsForExemption 1 param → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Exemption (7 properties), Page (5 properties), ExemptionRequest (5 properties), Attachment (4 properties). Each schema is shown below with its type and property counts.

ExemptionRequest
object
5 properties 2 required
Attachment
object
4 properties
ExemptionPage
Error
object
2 properties
Exemption
object
7 properties
Page
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kintsugi-exemptions-api-openapi.yml Raw ↑

Other APIs Kintsugi publishes across the network.

Kintsugi Address Validation API
Kintsugi Customers API
Kintsugi Filings API
Kintsugi Nexus API
Kintsugi Products API
Kintsugi Registrations API
Kintsugi Tax Estimation API
Kintsugi Transactions API
Where this information came from

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