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

Wealth Reader Advanced API

Optional endpoints not required for standard integrations. Use only if explicitly instructed by Wealth Reader.

Wealth Reader Advanced 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 Advanced. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, pricing, a support channel, and authentication docs.

This API exposes 8 operations across 8 paths, and defines 52 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/.

8 operations 8 paths 52 schemas 1 GET7 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/
Resource Areas
1

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 1 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Advanced 8

Optional endpoints not required for standard integrations. Use only if explicitly instructed by Wealth Reader.

GET
/entities/
Retrieves the list of supported entities
getEntities 1 param → 200400
POST
/verify/iban-ownership/
Verify bank account ownership via IBAN
postVerifyIbanOwnership body → 200400
POST
/user/register/
Register a new user
registerUser body → 200400401
POST
/user/check/
Check user registration status
checkUser body → 200400401
POST
/user/revoke/
Revoke a previously registered user
revokeUser body → 200400401
POST
/batch/load/
Batch connection loading
postBatchLoad body → 202400401
POST
/batch/fetch/statistics/
Get general statistics about batch connections
postBatchFetchStatistics body → 200404
POST
/batch/fetch/connection-result/
Get individual result of a specific connection within a batch
postBatchFetchConnectionResult body → 200400404

Schemas 52

The contract defines 52 schemas that model the data the API accepts and returns. The most detailed are portfolio_common (17 properties), batch-connection (15 properties), portfolio_composition_bonds_item (14 properties), user_information (13 properties). Each schema is shown below with its type and property counts.

cards
array
portfolio_composition_bonds
array
Composition for subtype=bonds
confirming
array
portfolio_composition_stocks_item
object
10 properties
lease_installment
object
9 properties 3 required
error-response
object
2 properties
entities
object
6 properties 6 required
accounts
array
portfolio_alternative_investments
factoring
array
portfolio_composition_crypto_item
object
10 properties
portfolio_composition_pension_plans
array
Composition for subtype=pension-plans
portfolio_bonds
owner
object
3 properties 3 required
guarantees
array
revoke-user-response
object
2 properties
portfolio_transactions
array
portfolios
array
Investment portfolios. Item schema depends on subtype.
portfolio_composition_funds_item
object
9 properties
register-user-request
object
4 properties 4 required
owners
array
Array of owners
user_information
object
Information related to the person logging in
13 properties 2 required
deposits
array
check-user-response
object
4 properties
portfolio_composition_funds
array
Composition for subtype=funds (and alternative-investments)
portfolio_funds
entity-data
object
3 properties 3 required
receipts
array
revoke-user-request
object
3 properties 3 required
register-user-response
object
2 properties
additional_info
array
insurances
array
error-detail
object
2 properties 2 required
properties
array
portfolio_stocks
files
array
portfolio_transaction
object
11 properties 7 required
portfolio_composition_stocks
array
Composition for subtype=stocks
statistics
object
5 properties 2 required
portfolio_common
object
Portfolio container. The fields available in composition depend on the subtype.
17 properties 14 required
portfolio_composition_bonds_item
object
14 properties
portfolio_pension_plans
contracts
array
check-user-request
object
2 properties 2 required
portfolio_crypto
batch-connection
object
Structure of each connection in the array - accepts all parameters from the /entities/ method Must always send credentialid + code + (token OR credentials)
15 properties 2 required
portfolio_composition_crypto
array
Composition for subtype=crypto
loans
array
employment
object
Employment history / work life and contributions
2 properties
portfolio_composition_pension_plans_item
object
9 properties
error
object
3 properties 3 required
leases
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wealth-reader-advanced-api-openapi.yml Raw ↑

Other APIs Wealth Reader publishes across the network.

Wealth Reader Cards (real time) API
Wealth Reader Core API
Where this information came from

This is an independent, third-party profile of Wealth Reader Advanced 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.