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

xdata-kr Auth Handoff API

The AuthHandoff API from xdata-kr — 1 operation(s) for authhandoff.

xdata-kr Auth Handoff API is one of 31 APIs that xdata-kr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

1 operations 1 paths 4 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Authentication
HTTP Basic, OAuth 2.0
Resource Areas
1

Authentication & Security 2

xdata-kr Auth Handoff API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicClientCredential). It supports OAuth 2.0 (mcpOAuth2) using the authorizationCode flow. By default, every request must be authenticated.

  • basicClientCredential — Console-issued client credential. Send Authorization: Basic base64(clientid:clientsecret).
  • mcpOAuth2 — For MCP clients. OAuth 2.0 authorization code flow with PKCE (S256) for public clients. The clientid is the HTTPS URL of an OAuth Client ID Metadata Document t…

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

AuthHandoff 1
POST
/v1/auth/handoff/exchange
Exchange one-time handoff token for client credentials (CR-FE-020)
post_auth_handoff_exchange_v1_auth_handoff_exchange_post 3 params body → 200422

Schemas 4

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

ValidationError
object
5 properties 3 required
AuthHandoffExchangeRequest
object
1 property 1 required
HTTPValidationError
object
1 property
AuthHandoffExchangeResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xdata-kr-authhandoff-api-openapi.yml Raw ↑

Other APIs xdata-kr publishes across the network.

xdata-kr App Credential API
xdata-kr Auth API
xdata-kr Billing Invoices API
xdata-kr Billing Payment Methods API
xdata-kr Billing Payments API
xdata-kr Billing Plans API
xdata-kr Billing Refunds API
xdata-kr Billing Standard Checkout API
xdata-kr Billing Subscriptions API
xdata-kr Billing Webhooks API
xdata-kr Composite Pack API
xdata-kr Console Self Service API
Where this information came from

This is an independent, third-party profile of xdata-kr Auth Handoff 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.