Order.co website screenshot

Order.co

Order.co (founded 2016 in New York as Negotiatus, rebranded to Order.co in 2021) is a procurement and finance-automation platform for mid-market and enterprise buyers: guided purchasing across a managed vendor catalog, purchase-order and approval workflow, accounts- payable automation, spend management and virtual cards, sold into multi-location operators in property management, hospitality, healthcare, retail, fitness, coworking, early childhood education, wellness, technology and nonprofit. The product connects to QuickBooks Online, NetSuite, Sage Intacct and Workday over API, and supports SSO through Okta and Ping Identity. Order.co publishes no developer portal, no API reference and no machine-readable specification for any of that - the procurement API is disclosed only to customers, and vendors receive API or EDI credentials during onboarding. What it does publish anonymously are two real, self-describing surfaces on its own hosts - the WordPress REST API behind www.order.co (blog, customer and vendor stories, ebooks, webinars, tools, 873 FAQ records, and the first-party industry and use-case taxonomies) and the Atlassian Statuspage v2 API on status.order.co - plus an llms.txt and a companion page written for language models.

Order.co publishes 14 APIs on the APIs.io network, including Components API, Content API, Customer Stories API, and 11 more. Tagged areas include Company, Procurement, Spend Management, Accounts Payable, and Purchasing.

Order.co’s developer surface includes authentication, code examples, engineering blog, and 21 more developer resources.

31.3/100 thin ▬ flat Agent 25/100 agent aware saas Full breakdown ↓
scored 2026-09-02 · rubric v0.18.0
AccessOpen
2 APIs
CompanyProcurementSpend ManagementAccounts PayablePurchasingVendor ManagementPaymentsVirtual CardsFinance AutomationUnited States

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-02 · rubric v0.18.0
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/orderco: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 14

Individual APIs this provider publishes, each with its own machine-readable definition.

Order.co Components API

The individual services Order.co reports health for.

Order.co Content API

Posts, pages and media.

Order.co Customer Stories API

Published Order.co customer case studies.

Order.co Discovery API

Self-describing route, type and taxonomy introspection.

Order.co FA Qs API

Question-and-answer entries used across the site.

Order.co Incidents API

Open and historical incidents with their dated updates.

Order.co Maintenance API

Scheduled maintenance windows.

Order.co Newsroom API

First-party cn/v1 theme namespace.

Order.co Resources API

Ebooks, webinars, tools and spend insights.

Order.co Search API

Cross-type search.

Order.co Status API

The rollup status indicator for the whole page.

Order.co Taxonomies API

Categories, tags, industries and use cases.

Order.co Testimonials API

Customer quotes.

Order.co Vendor Stories API

Published Order.co vendor/supplier case studies.

Scroll for all 14

Open Collections 15

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Order.co Content API

OPEN COLLECTION

Order.co Status API

OPEN COLLECTION

Scroll for all 15

Examples 11

Example request and response payloads for these APIs.

Orderco Content Discovery

16 fields

EXAMPLE

Orderco Content Types

19 fields

EXAMPLE

Orderco Status Components

2 fields

EXAMPLE

Orderco Status Incidents

2 fields

EXAMPLE

Orderco Status Status

2 fields

EXAMPLE

Orderco Status Summary

5 fields

EXAMPLE

Scroll for all 11

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Orderco Authentication

0 schemes

SECURITY

Orderco Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 2

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 6

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: orderco
name: Order.co
description: 'Order.co (founded 2016 in New York as Negotiatus, rebranded to Order.co in 2021) is a procurement and finance-automation
  platform for mid-market and enterprise buyers: guided purchasing across a managed vendor catalog, purchase-order and approval
  workflow, accounts- payable automation, spend management and virtual cards, sold into multi-location operators in property
  management, hospitality, healthcare, retail, fitness, coworking, early childhood education, wellness, technology and nonprofit.
  The product connects to QuickBooks Online, NetSuite, Sage Intacct and Workday over API, and supports SSO through Okta and
  Ping Identity. Order.co publishes no developer portal, no API reference and no machine-readable specification for any of
  that - the procurement API is disclosed only to customers, and vendors receive API or EDI credentials during onboarding.
  What it does publish anonymously are two real, self-describing surfaces on its own hosts - the WordPress REST API behind
  www.order.co (blog, customer and vendor stories, ebooks, webinars, tools, 873 FAQ records, and the first-party industry
  and use-case taxonomies) and the Atlassian Statuspage v2 API on status.order.co - plus an llms.txt and a companion page
  written for language models.'
url: https://raw.githubusercontent.com/api-evangelist/orderco/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: enriched
x-tier-reason: enrichment-pipeline
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 35
  pass: local-v1
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  label: Open access
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-02'
  method: derived
image: https://www.order.co/wp-content/themes/order/assets/img/logos/order.svg
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Procurement
- Spend Management
- Accounts Payable
- Purchasing
- Vendor Management
- Payments
- Virtual Cards
- Finance Automation
- United States
apis:
- aid: orderco:orderco-components-api
  name: Order.co Components API
  description: The individual services Order.co reports health for.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Components
  properties:
  - type: OpenAPI
    url: openapi/orderco-components-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-content-api
  name: Order.co Content API
  description: Posts, pages and media.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Content
  properties:
  - type: OpenAPI
    url: openapi/orderco-content-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-customer-stories-api
  name: Order.co Customer Stories API
  description: Published Order.co customer case studies.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Customer Stories
  properties:
  - type: OpenAPI
    url: openapi/orderco-customer-stories-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-discovery-api
  name: Order.co Discovery API
  description: Self-describing route, type and taxonomy introspection.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Discovery
  properties:
  - type: OpenAPI
    url: openapi/orderco-discovery-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-faqs-api
  name: Order.co FA Qs API
  description: Question-and-answer entries used across the site.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - FAQs
  properties:
  - type: OpenAPI
    url: openapi/orderco-faqs-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-incidents-api
  name: Order.co Incidents API
  description: Open and historical incidents with their dated updates.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Incidents
  properties:
  - type: OpenAPI
    url: openapi/orderco-incidents-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-maintenance-api
  name: Order.co Maintenance API
  description: Scheduled maintenance windows.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Maintenance
  properties:
  - type: OpenAPI
    url: openapi/orderco-maintenance-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-newsroom-api
  name: Order.co Newsroom API
  description: First-party cn/v1 theme namespace.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Newsroom
  properties:
  - type: OpenAPI
    url: openapi/orderco-newsroom-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-resources-api
  name: Order.co Resources API
  description: Ebooks, webinars, tools and spend insights.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Resources
  properties:
  - type: OpenAPI
    url: openapi/orderco-resources-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-search-api
  name: Order.co Search API
  description: Cross-type search.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Search
  properties:
  - type: OpenAPI
    url: openapi/orderco-search-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-status-api
  name: Order.co Status API
  description: The rollup status indicator for the whole page.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Status
  properties:
  - type: OpenAPI
    url: openapi/orderco-status-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-taxonomies-api
  name: Order.co Taxonomies API
  description: Categories, tags, industries and use cases.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - taxonomies
  tags_raw:
  - Taxonomies
  properties:
  - type: OpenAPI
    url: openapi/orderco-taxonomies-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-testimonials-api
  name: Order.co Testimonials API
  description: Customer quotes.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Testimonials
  properties:
  - type: OpenAPI
    url: openapi/orderco-testimonials-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-vendor-stories-api
  name: Order.co Vendor Stories API
  description: Published Order.co vendor/supplier case studies.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Vendor Stories
  properties:
  - type: OpenAPI
    url: openapi/orderco-vendor-stories-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/orderco-content-overlay.yaml
- type: Authentication
  url: authentication/orderco-authentication.yml
- type: Conventions
  url: conventions/orderco-conventions.yml
- type: ErrorCatalog
  url: errors/orderco-problem-types.yml
- type: Lifecycle
  url: lifecycle/orderco-lifecycle.yml
- type: StatusPage
  url: https://status.order.co/
- type: Conformance
  url: conformance/orderco-conformance.yml
- type: DataModel
  url: data-model/orderco-data-model.yml
- type: DomainSecurity
  url: security/orderco-domain-security.yml
- type: WellKnown
  url: well-known/orderco-well-known.yml
- type: LLMsTxt
  url: llms/orderco-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Examples
  url: examples/orderco-content-discovery.json
- type: Website
  url: https://www.order.co/
- type: Blog
  url: https://www.order.co/blog/
- type: BlogRSS
  url: https://www.order.co/blog/feed/
- type: Login
  url: https://app.order.co/login
- type: GitHubOrganization
  url: https://github.com/Negotiatus
- type: LinkedIn
  url: https://www.linkedin.com/company/order-company
- type: PrivacyPolicy
  url: https://www.order.co/privacy-policy/
- type: TermsOfService
  url: https://www.order.co/terms-and-conditions/
- type: Careers
  url: https://www.order.co/careers/
- type: Press
  url: https://www.order.co/newsroom/
- type: Demo
  url: https://www.order.co/demo/
- type: Integrations
  url: https://www.order.co/accounting-integrations/

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/orderco"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/orderco/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/orderco/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.