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

Emboss Pay API

The Pay API from Emboss — 7 operation(s) for pay.

Emboss Pay API is one of 23 APIs that Emboss publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Pay. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

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

Requests are made against the base URL https://api.getemboss.ai.

7 operations 7 paths 4 schemas 5 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.getemboss.ai
Authentication
HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 2

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

  • bearer — An Emboss API key. See https://getemboss.ai/docs/authentication.
  • oauth2 — Sign in with your Emboss account. See https://getemboss.ai/docs/authentication.

Paths & Operations 7

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

Pay 7
GET
/pay
Pay Index
pay_index_pay_get → 200
GET
/pay/openapi.json
Pay Openapi Manifest
pay_openapi_manifest_pay_openapi_json_get → 200
GET
/pay/llms.txt
Pay Llms Txt
pay_llms_txt_pay_llms_txt_get → 200
GET
/pay/pricing
Pay Pricing Alias
pay_pricing_alias_pay_pricing_get → 200
POST
/pay/quote
Pay Quote
pay_quote_pay_quote_post body → 200422
POST
/pay/{op}
Pay
pay_pay__op__post 1 param body → 200422
GET
/pay/jobs/{job_id}
Pay Job Status
pay_job_status_pay_jobs__job_id__get 2 params → 200422

Schemas 4

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

Body_pay_pay__op__post
object
9 properties
ValidationError
object
5 properties 3 required
Body_pay_quote_pay_quote_post
object
5 properties
HTTPValidationError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

getemboss-ai-pay-api-openapi.yml Raw ↑

Other APIs Emboss publishes across the network.

Emboss MCP Server
Emboss A2A Agent
Emboss Admin API
Emboss App API
Emboss Artifacts API
Emboss D API
Emboss Fax API
Emboss Forms API
Emboss Health API
Emboss Keys API
Emboss Library API
Emboss OAuth API
Where this information came from

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