obapi.org valid

OpenBusinessAPI (OBAPI)

OBAPI is an open standard REST API for B2B document exchange -- invoices, orders, proposals and more

For agents: OBAPI is an open REST API standard for B2B document exchange of invoices, orders and proposals, with machine-readable spec entry points designed for AI coding a

b2b document exchangerest apiinvoicespurchase ordersbearer token authopenbusinessapi

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T00:00:12.093Z. Cached copy · Source on obapi.org

# OpenBusinessAPI (OBAPI)

> OBAPI is an open standard REST API for B2B document exchange -- invoices, orders, proposals and more

OBAPI defines a unified REST API so any compatible provider can expose its business documents (invoices, orders, proposals, and more) through one standard interface. This file is a curated map of the specification for AI agents and tools: fetch the linked pages, or grab the whole spec at once from https://obapi.org/llms-full.txt.

The OpenAPI document at https://obapi.org/assets/openapi.yaml is the machine-readable source of truth for endpoints, request and response schemas.

## Guides

- [For AI Agents](https://obapi.org/v1/for-ai-agents): OBAPI is designed to be implemented with the help of an AI coding assistant. The whole specification is exposed as machine-readable, single-URL entry points so you can hand an agent one link and let it do the work.
- [Workflows](https://obapi.org/v1/workflows): Understanding how OBAPI objects relate to each other and how documents flow through their lifecycle.
- [Getting Started](https://obapi.org/v1/getting-started): Get your first OBAPI response in 5 minutes.

## Transversal

- [Authentication](https://obapi.org/v1/auth): Authentication is done via Bearer token. The enrollment process (how you obtain the token) is outside the scope of OBAPI -- each provider decides: login/password with JWT, pre-shared key, OAuth2, etc.
- [Discovery](https://obapi.org/v1/discovery): The discovery endpoint lets a client know which objects and capabilities a given OBAPI server supports. Not every server will implement all tiers.
- [Errors](https://obapi.org/v1/errors): OBAPI uses conventional HTTP response codes and a structured JSON error body.

## Tier 1 -- Core

- [Thirdparty](https://obapi.org/v1/thirdparty): The provider's identity. Unlike other objects, this endpoint is singular -- it returns who owns this OBAPI server.
- [Contacts](https://obapi.org/v1/contacts): Contact persons associated with the provider.
- [Products](https://obapi.org/v1/products): Product and service catalog.
- [Proposals](https://obapi.org/v1/proposals): Sales quotation / devis.
- [Orders](https://obapi.org/v1/orders): Customer orders.
- [Invoices](https://obapi.org/v1/invoices): Customer invoices. This is the original and primary OBAPI use case.
- [Credit Notes](https://obapi.org/v1/creditnotes): Credit note / avoir. Same structure as Invoice with type always set to creditnote.
- [Shipments](https://obapi.org/v1/shipments): Delivery / despatch advice. Represents goods shipped to the customer.
- [Download](https://obapi.org/v1/download): Generic document download. Returns the binary PDF for any OBAPI object.

## Tier 2 -- Extended

- [Supplier Proposals](https://obapi.org/v1/supplier-proposals): Request for quotation / price request sent to a supplier.
- [Supplier Orders](https://obapi.org/v1/supplier-orders): Purchase orders sent to suppliers.
- [Supplier Invoices](https://obapi.org/v1/supplier-invoices): Invoices rece
…

Related sites

Find similar publishers by meaning →

Other listed sites in APIs and SDKs. See the whole category →

Machine-readable: GET /v1/resolve?q=obapi.org · GET /v1/domain/obapi.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for obapi.org:
1. POST https://agentwebmap.com/v1/sites/obapi.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://obapi.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/obapi.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/obapi.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.