Procuros
Procuros is a Hamburg-based B2B digital trade platform that connects suppliers with retailers and logistics partners through automated document exchange. A single connection lets trading partners exchange orders, order responses, invoices, credit notes, shipping notices, dispatch instructions, product catalogs and more — whether the partner runs EDI (AS2, SFTP, X.400), PDFs, or Excel. Procuros offers ERP connectors (SAP, Microsoft Business Central, Oracle, Odoo, Weclapp, Xentral, JTL), an AI-powered Order Agent for PDF/email orders, e-invoicing compliance (ZUGFeRD, X-Rechnung, PEPPOL), logistics automation and payment reconciliation. Its REST API v2 lets integrators list incoming transactions, send outgoing transactions, mark documents processed, and report errors — backed by an OpenAPI 3.0.3 spec, cursor pagination, Bearer-token auth, and a staging environment. Backed by Creandum and Point Nine.
Procuros publishes 4 API contracts indexed on the APIs.io network, including All Transactions API, Incoming Transactions API, Misc API, and 1 more. Tagged areas include Company, Software-as-a-Service, EDI, E-Invoicing, and Supply Chain.
The Procuros catalog on APIs.io includes 1 Spectral governance ruleset.
Procuros’ developer surface includes documentation, API reference, getting-started guide, engineering blog, authentication, changelog, sandbox, and 17 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Procurement and B2B Buying (source-to-pay suites, spend management) | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 4
Individual APIs this provider publishes, each with its own machine-readable definition.
Procuros All Transactions API
The All Transactions API from Procuros — 2 operation(s) for all transactions.
Procuros Incoming Transactions API
The Incoming Transactions API from Procuros — 3 operation(s) for incoming transactions.
Procuros Misc API
The Misc API from Procuros — 1 operation(s) for misc.
Procuros Outgoing Transactions API
The Outgoing Transactions API from Procuros — 2 operation(s) for outgoing transactions.
Open Collections 4
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Procuros All Transactions API
OPEN COLLECTIONProcuros All Transactions Incoming Transactions API
OPEN COLLECTIONProcuros All Transactions Misc API
OPEN COLLECTIONProcuros All Transactions Outgoing Transactions API
OPEN COLLECTIONAgent Skills 2
Packaged agent skills for driving this provider's APIs from an AI assistant.
Process incoming transactions
AGENT SKILLSend a transaction to a trade partner
AGENT SKILLSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
Procuros API Rules
SPECTRALOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Procuros V2 Overlay
DERIVEDSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Procuros API — frequently asked questions
Does Procuros have an API?
Yes. APIs.io lists 4 APIs from Procuros, including Procuros All Transactions API, Procuros Incoming Transactions API and Procuros Misc API, and 1 more.
Is there an OpenAPI specification for the Procuros API?
Yes. APIs.io indexes 4 OpenAPI specifications for Procuros, each linked for download from this page.
How do I authenticate with the Procuros API?
Procuros uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Procuros Authentication.
Is the Procuros API ready for AI agents?
Procuros has a Kin Score of 43.1 out of 100 (developing) and an Agent Readiness score of 32.8 (agent-ready), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.