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

Yarnhen OAuth API

OAuth 2.1 for MCP clients: register, send the account owner to approve in the browser, and exchange the code for scoped tokens. For the client and the human, not agent tools.

Yarnhen OAuth API is one of 5 APIs that Yarnhen publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include OAuth and Authentication. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against 4 base URLs: https://yawplet.com, https://yarnhen.com, https://hagglebee.com, https://eventwren.com.

6 operations 6 paths 7 schemas 1 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Servers
https://yawplet.com
https://yarnhen.com
https://hagglebee.com
https://eventwren.com
Authentication
HTTP Bearer, OAuth 2.0
License
Apache-2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

Yarnhen OAuth API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (apiKey). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 5 scopes. By default, every request must be authenticated.

  • apiKey — API key from POST /v1/accounts. Not scoped: full access to its account.
  • oauth2 — OAuth 2.1 for MCP clients: authorization code with PKCE (S256 only), public clients registered with RFC 7591, opaque access tokens (one hour) and rotating refr…

Paths & Operations 6

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

OAuth 6

OAuth 2.1 for MCP clients: register, send the account owner to approve in the browser, and exchange the code for scoped tokens. For the client and the human, not agent tools.

POST
/v1/oauth/register
Register an OAuth client (RFC 7591 dynamic client registration)
registerOAuthClient body → 201400429
GET
/v1/oauth/authorize
Start an authorization (OAuth 2.1 authorization endpoint, PKCE required)
authorizeOAuth 8 params → 302400
POST
/v1/oauth/login
Email the account owner a sign-in link back to the consent page
requestOAuthConsentLink body → 200400429
POST
/v1/oauth/approve
Approve or deny an authorization (the account owner's decision)
decideOAuthConsent 1 param body → 200400401403
POST
/v1/oauth/token
Exchange a code or a refresh token for tokens (OAuth 2.1 token endpoint)
exchangeOAuthToken body → 200400401
POST
/v1/oauth/revoke
Revoke an access or refresh token (RFC 7009)
revokeOAuthToken body → 200400

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are OAuthTokenRequest (8 properties), OAuthClient (8 properties), Error (6 properties), OAuthClientRegistration (5 properties). Each schema is shown below with its type and property counts.

OAuthToken
object
5 properties 4 required
OAuthClient
object
8 properties
Error
object
RFC 9457 problem details. The legacy error object carries the same code and message.
6 properties
OAuthTokenRequest
object
8 properties 2 required
OAuthClientRegistration
object
5 properties 1 required
OAuthRevokeRequest
object
3 properties 1 required
OAuthError
object
An OAuth error (RFC 6749 §5.2, RFC 7591 §3.2.2), the shape OAuth client libraries parse. Used only by the token, register and revoke endpoints.
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yarnhen-oauth-api-openapi.yml Raw ↑

Other APIs Yarnhen publishes across the network.

Yarnhen Accounts API
Yarnhen Discovery API
Yarnhen Posts API
Yarnhen Webhooks API
Where this information came from

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