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

yappy-biz Exports API

Asynchronous corpus exports.

yappy-biz Exports API is one of 7 APIs that yappy-biz publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Export. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

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

Requests are made against 2 base URLs: https://yappy.biz/api/v1, https://yappy.biz/api/v1/sandbox.

2 operations 2 paths 3 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://yappy.biz/api/v1
Authentication
HTTP Bearer, OAuth 2.0
License
Proprietary — LicenseRef-Proprietary
Terms of Service
Resource Areas
1

Authentication & Security 2

yappy-biz Exports API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (opaque) (bearerAuth). It supports OAuth 2.0 (oauth2) using the clientCredentials and authorizationCode flows, exposing 5 scopes. By default, every request must be authenticated, though some operations may also be called without credentials.

  • bearerAuth — An access token from /oauth/token. Optional — every read endpoint also answers anonymously.
  • oauth2 — OAuth 2.1 with PKCE S256. Dynamic client registration (RFC 7591) at /oauth/register; no human approval step.

Paths & Operations 2

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

Exports 2

Asynchronous corpus exports.

POST
/exports
Start an export job
createExport 1 param body → 202409415400401403429500
GET
/exports/{job_id}
Poll an export job
getExport 1 param → 200404400401403429500503

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Job (10 properties), Problem (9 properties), ExportRequest (2 properties). Each schema is shown below with its type and property counts.

Job
object
An asynchronous export. Poll until status is completed, then read result.url.
10 properties 5 required
Problem
object
RFC 9457 problem details. Branch on code, which is stable; title and detail are prose for a human or for an agent explaining itself.
9 properties 4 required
ExportRequest
object
What to export, and in which format.
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yappy-biz-exports-api-openapi.yml Raw ↑

Other APIs yappy-biz publishes across the network.

yappy-biz Batch API
yappy-biz Commerce API
yappy-biz Discovery API
yappy-biz Documentation API
yappy-biz Product API
yappy-biz Releases API
Where this information came from

This is an independent, third-party profile of yappy-biz Exports 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.