Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Reachware Inc. Cards API

Card save / tokenization flows

Reachware Inc. Cards API is one of 2 APIs that Reachware Inc. publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 1 operation across 1 path, and defines 1 schema. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against a single base URL, https://api.reachware.com.

1 operations 1 paths 1 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.reachware.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Reachware Inc. Cards API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Merchant API token: Authorization: Bearer {reachToken}

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Cards 1

Card save / tokenization flows

POST
/pay/RequestSaveCard
Save Cards
requestSaveCard body → 200400404

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is ErrorFlag (2 properties). Each schema is shown below with its type and property counts.

ErrorFlag
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

reachware-inc-cards-api-openapi.yml Raw ↑

Other APIs Reachware Inc. publishes across the network.

Reachware Inc. Payments API