Reachware

Reachware is an Integration Platform as a Service (iPaaS) that lets separate SaaS and business systems operate as one connected ecosystem, with 200+ prebuilt connectors to systems like NetSuite, QuickBooks, Microsoft Dynamics 365, Odoo, SAP, Oracle, Magento, Zid and Qoyod. Alongside the core platform it ships Reach Pay (a payment API for Saudi Arabia payment gateways), Reachware Fatoora (ZATCA e-invoicing), and extension modules for banking, HR, inventory, loyalty and property management. Reach Pay exposes a hosted-redirect REST API for requesting payments, retrieving payment details, refunds and card tokenization. Reachware reports 3,500+ active subscriptions, 300+ customers, 100M+ transactions, and is CMMI Level 3 certified. It was surfaced as a portfolio company of 500 Global and profiled by the API Evangelist enrichment pipeline.

Reachware publishes 2 API contracts indexed on the APIs.io network: Inc. Cards API and Inc. Payments API. Tagged areas include Company, Payments, iPaaS, Integration, and Fintech.

The Reachware catalog on APIs.io includes 1 Spectral governance ruleset.

Reachware’s developer surface includes engineering blog, authentication, sandbox, documentation, API reference, getting-started guide, support, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

42.8/100 developing ▬ flat Agent 26/100 agent aware Front door AI 3/6 light Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 2 Agent Skills

Company Payments iPaaS Integration Fintech Payment Gateway Tokenization Saudi Arabia

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Subscription Billing & Revenue Management

BC-4250

Payments

POST /pay/RequestPayment GET /pay/PaymentDetails POST /pay/Refund

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 42.8/100 · developing

Contract Quality 9.4 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 3.8 / 15

Operational Transparency 0.0 / 10

Contract Governance 2.9 / 9

Discoverability 5.5 / 8

Regulatory Posture 4.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/reachware-inc/"><img src="https://apis.io/badge/reachware-inc/card.svg" alt="Reachware on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 25.0 — up to +15.0 composite points
Operational Transparency scores 0.0 — up to +13.0 composite points
Contract Quality scores 50.2 — up to +12.5 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/reachware-inc/apis.yml: open an issue on github.com/api-evangelist/reachware-inc to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 2

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

Reachware Inc. Cards API

Card save / tokenization flows

Reachware Inc. Payments API

Request payments, retrieve payment details, and refunds

Open Collections 2

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

Reach Pay Cards API

OPEN COLLECTION

Reach Pay Cards Payments API

OPEN COLLECTION

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Accept a payment with Reach Pay

AGENT SKILL

Refund a Reach Pay payment

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Reachware API Rules

57 rules · 55 errors 1 warnings 1 info

SPECTRAL

OpenAPI 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.

Reachware Inc Reachpay Overlay

2 actions · update · reachware-inc-reachpay-openapi.yml

DERIVED

Security Posture 2

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

Reachware Inc Authentication

http · 1 scheme

SECURITY

Reachware Inc Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

Sandbox

Sandbox

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Documentation 3

Reference material describing how the API behaves

OpenAPI

OpenAPI

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

DataModel

Conformance

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Compliance

Compliance

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: reachware-inc
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: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/reachware-inc.png
name: Reachware
description: Reachware is an Integration Platform as a Service (iPaaS) that lets separate SaaS and business systems operate
  as one connected ecosystem, with 200+ prebuilt connectors to systems like NetSuite, QuickBooks, Microsoft Dynamics 365,
  Odoo, SAP, Oracle, Magento, Zid and Qoyod. Alongside the core platform it ships Reach Pay (a payment API for Saudi Arabia
  payment gateways), Reachware Fatoora (ZATCA e-invoicing), and extension modules for banking, HR, inventory, loyalty and
  property management. Reach Pay exposes a hosted-redirect REST API for requesting payments, retrieving payment details, refunds
  and card tokenization. Reachware reports 3,500+ active subscriptions, 300+ customers, 100M+ transactions, and is CMMI Level
  3 certified. It was surfaced as a portfolio company of 500 Global and profiled by the API Evangelist enrichment pipeline.
url: https://raw.githubusercontent.com/api-evangelist/reachware-inc/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: profiled
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Company
- Payments
- iPaaS
- Integration
- Fintech
- Payment Gateway
- Tokenization
- Saudi Arabia
apis:
- aid: reachware-inc:reachware-inc-cards-api
  name: Reachware Inc. Cards API
  description: Card save / tokenization flows
  humanURL: https://docs.reachware.com
  baseURL: https://api.reachware.com
  tags:
  - Cards
  properties:
  - type: OpenAPI
    url: openapi/reachware-inc-cards-api-openapi.yml
  - type: Documentation
    url: https://docs.reachware.com
  - type: GettingStarted
    url: https://docs.reachware.com/docs/getting-started.md
  - type: APIReference
    url: https://docs.reachware.com/reference/reach-pay-checkout.md
- aid: reachware-inc:reachware-inc-payments-api
  name: Reachware Inc. Payments API
  description: Request payments, retrieve payment details, and refunds
  humanURL: https://docs.reachware.com
  baseURL: https://api.reachware.com
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/reachware-inc-payments-api-openapi.yml
  - type: Documentation
    url: https://docs.reachware.com
  - type: GettingStarted
    url: https://docs.reachware.com/docs/getting-started.md
  - type: APIReference
    url: https://docs.reachware.com/reference/reach-pay-checkout.md
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://reachware.com/blog
  type: Blog
- type: CapabilityMap
  url: capabilities/reachware-inc-capability-edges.yml
  name: Reachware Business Capability Map
- type: OpenAPI
  url: openapi/_original/reachware-inc-reachpay-openapi.yml
- type: Overlay
  url: overlays/reachware-inc-reachpay-overlay.yaml
- type: Authentication
  url: authentication/reachware-inc-authentication.yml
- type: DomainSecurity
  url: security/reachware-inc-domain-security.yml
- type: X-MCPServerCandidate
  url: mcp/reachware-inc-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: ErrorCatalog
  url: errors/reachware-inc-problem-types.yml
- type: Conventions
  url: conventions/reachware-inc-conventions.yml
- type: DataModel
  url: data-model/reachware-inc-data-model.yml
- type: Sandbox
  url: sandbox/reachware-inc-sandbox.yml
- type: Conformance
  url: conformance/reachware-inc-conformance.yml
- type: Compliance
  url: conformance/reachware-inc-conformance.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/reachware-inc-llms.txt
- type: DeveloperPortal
  url: https://docs.reachware.com
- type: Documentation
  url: https://docs.reachware.com
- type: APIReference
  url: https://docs.reachware.com/reference/reach-pay-checkout.md
- type: GettingStarted
  url: https://docs.reachware.com/docs/getting-started.md
- type: Support
  url: mailto:support@reachware.com
- type: Login
  url: https://app.reachware.com/
- type: TermsOfService
  url: https://reachware.com/terms-of-service
- type: PrivacyPolicy
  url: https://reachware.com/privacy-policy
- type: Website
  url: https://reachware.com
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 14
  pass: local-v1
x-legal-name: Reachware Inc.

Reachware API — frequently asked questions

Does Reachware have an API?

Yes. APIs.io lists 2 APIs from Reachware, including Reachware Inc. Cards API and Reachware Inc. Payments API.

Is there an OpenAPI specification for the Reachware API?

Yes. APIs.io indexes 2 OpenAPI specifications for Reachware, each linked for download from this page.

How do I authenticate with the Reachware API?

Reachware uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Reachware Inc Authentication.

Is the Reachware API ready for AI agents?

Reachware has a Kin Score of 42.8 out of 100 (developing) and an Agent Readiness score of 25.5 (agent-aware), 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.

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/reachware-inc"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/reachware-inc/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/reachware-inc/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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