How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Wealth Reader

Wealth Reader Cards (real time) API

Real-time card expense synchronization from the Open Sync mobile app: per-customer employee pre-registration, signed webhooks (card_transaction.created / card_enrollment.confirmed), and REST query / backfill.

Documentation Provider Profile APIs.io OpenAPI GitHub

Wealth Reader Cards (real time) API is one of 3 APIs that Wealth Reader publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cards (real time). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, pricing, a support channel, and authentication docs.

This API exposes 4 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 8.1.7.

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

4 operations 3 paths 4 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
8.1.7
Base URL
https://api.wealthreader.com/
Contact
info@wealthreader.com
Resource Areas
1

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Cards (real time) 4

Real-time card expense synchronization from the Open Sync mobile app: per-customer employee pre-registration, signed webhooks (cardtransaction.created / cardenrollment.confirmed),…

POST
/cards/webhook/
Register or rotate the real-time cards webhook
cardsWebhookRegister body → 200400401
POST
/cards/enrollments/
Pre-register the email of an employee
cardsEnrollmentsCreate body → 200400401409429
GET
/cards/enrollments/
Check the status of an enrollment
cardsEnrollmentsStatus 2 params → 200401404
GET
/cards/transactions/
Query / backfill real-time card transactions
cardsTransactionsList 6 params → 200400401

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are cards-transaction (15 properties), cards-enrollment (6 properties), cards-webhook-delivery (5 properties), cards-enrollment-response (2 properties). Each schema is shown below with its type and property counts.

cards-enrollment
object
Enrollment object. Same format returned inside the payload of POST and GET /cards/enrollments/ and sent as data in the cardenrollment.confirmed webhook.
6 properties
cards-transaction
object
Real-time card transaction object. Same format returned by GET /cards/transactions/ and sent in the cardtransaction.created webhook.
15 properties
cards-webhook-delivery
object
Body sent by Wealthreader to the webhookurl of the customer (POST /cards/webhook/) for the cardtransaction.created and cardenrollment.confirmed events. Headers…
5 properties 5 required
cards-enrollment-response
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wealth-reader-cards-real-time-api-openapi.yml Raw ↑

Other APIs Wealth Reader publishes across the network.

Wealth Reader Advanced API
AE Profile APIs.io
Wealth Reader Core API
AE Profile APIs.io
#Cards (real time)
← Back to W APIs
API Details
ID
wealth-reader:wealth-reader-cards-real-time-api
Base URL
https://api.wealthreader.com/
Docs
https://www.wealthreader.com/docs/en/introduction/
Provider
Wealth Reader
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=wealth-reader-cards-real-time-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/wealth-reader-cards-real-time-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Wealth Reader Cards (real time) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.