Repository navigation
Expand file tree
/
Copy pathapi-for-ai.yaml
More file actions
4974 lines (4947 loc) · 164 KB
/
Copy pathapi-for-ai.yaml
File metadata and controls
4974 lines (4947 loc) · 164 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
openapi: 3.0.0
info:
description: >
Regulatory APIs based on PSD2 provide access to certain financial
information such as bank account balances and transactions. However, there
are other sources of wealth information that are not accessible through
these APIs. The Wealth Reader API extends the information offered by
regulatory APIs by providing real-time access to additional wealth sources
in any entity worldwide. There are two other related documents that will
help you integrate the Wealth Reader API. One is the Javascript widget
integration guide: https://docs-en.wealthreader.com/ and the other is a
Postman collection based on this documentation.
Very important: This API definition is adapted for clients integrating via
Widget, so some parameters that are not necessary for this type of
integration have been omitted, such as bank authentication parameters, as a
token will be used.
version: 8.1.7
title: Wealth Reader
contact:
email: info@wealthreader.com
tags:
- name: Core
description: Core API required for standard integrations
- name: Advanced
description: >-
Optional endpoints not required for standard integrations. Use only if
explicitly instructed by Wealth Reader.
- name: Cards (real time)
description: >
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.
paths:
/entities/:
post:
tags:
- Core
summary: Retrieves financial assets and their composition details
description: >
Retrieves financial assets and details of their composition including
investment portfolios (stocks, funds, bonds, pension plans, alternative
investments, crypto), credit cards, insurance, and loans. Includes
ownership information for each asset as well as unique identifiers that
facilitate data processing. It is possible to obtain Mock data. Check
with the technical team on how to do this.
requestBody:
content:
application/x-www-form-urlencoded:
schema:
type: object
properties:
api_key:
type: string
description: Identifies the client in the service
example: a1b2c3d4e5f6g7h8i9j0
code:
type: string
description: Name of the entity. The complete list is available with GET
example: caixabank
token:
type: string
description: >-
Identifies the custodied credential. The flow by which the
token has been obtained is described in the 'Widget
Integration Guide' document. The following Mock users are
available: MOCKDATA, OK response; MOCKOTP, response with OTP
challenge; MOCKLOGINKO, response with login error
example: MOCKDATA
product_types:
type: string
enum:
- accounts
- portfolios
- cards
- receipts
- loans
- factoring
- confirming
- properties
- invoices
- files
- deposits
- leases
- insurances
description: >-
List of product types from which information is to be
retrieved. Accepts multiple values separated by commas.
example: accounts,portfolios
only_balances:
type: boolean
default: false
description: >-
Indicates whether to obtain only the balances of the
products instead of all available information. Default
value: false.
example: false
fetch_transaction_details:
type: boolean
default: false
description: >-
Indicates whether extended transaction details should be
retrieved when the entity connector supports it. IMPORTANT:
Enabling it implies performing one or more additional
navigations per transaction to enrich the returned
information. This will inevitably and significantly increase
the execution time. The number of additional navigations
grows with the volume of transactions. It is recommended to
enable it only when you are certain that a level of detail
beyond the one returned by default is required. The
retrieved details are inserted into the `additional_info`
key at the level of each transaction. The use of this
parameter requires a dedicated environment.
example: false
date_from:
type: string
format: date
description: >-
Date from which transactions are requested, in YYYY-MM-DD
format. Must be a date before today.
example: '2024-01-01'
date_to:
type: string
format: date
description: >-
This only applies to restricting by future dates for
products loan and confirming, in YYYY-MM-DD format. The date
must be later than today
example: '2025-12-31'
required_products_schema:
type: string
description: >-
Required products schema. Indicates the accounts or cards
from which data is desired, with additional configurations.
example: >-
{"ACCOUNTS":{"0ae4d722b1c82feeafb4b36b2893230444071335":{"only_balances":false,"add_pdf_from_uuids":["90763109952d4f2ebece8dceca8254078c5384a0"],"date_from":"2024-04-03"}},"CARDS":{"957e6f63546f3fecacce80192b6f7436496dc057":{}}}
add_pdf_from_uuids:
type: string
description: >-
Accepts transaction uuids separated by commas. Parameter
that is only taken into account if product_types is ALL or
includes accounts. Adds the PDF document associated with
each of the requested bank transactions.
example: >-
20966426721d0885ef9d4b95535e1d3198936f16,8772d6c978d37d7af83094abf380b8b703e94105,e59296b79e7f80cec26679d2c65883025fd59295
otp_method:
type: string
description: >-
Selects which second-factor delivery channel to use when the
API returned error code 2017 or 20171 (multiple OTP methods
available). Call again with the same session identifier from
that response and set this form field to the exact value of
the otp_method property from one object in
statistics.otpMethods (not the array index). Omit on the
first credential-based request; send after the end user
chooses a method. The example value below is illustrative
only—always copy the string returned in
statistics.otpMethods for your entity (wording may be
OTP_SMS ****1234, SMS *****1234, or another label depending
on the bank).
example: OTP_SMS ****1234
example:
api_key: a1b2c3d4e5f6g7h8i9j0
code: caixabank
token: 1234Asdf
product_types: accounts,portfolios
only_balances: false
date_from: '2024-01-01'
date_to: '2025-12-31'
required_products_schema: >-
{"ACCOUNTS":{"0ae4d722b1c82feeafb4b36b2893230444071335":{"only_balances":false,"add_pdf_from_uuids":["90763109952d4f2ebece8dceca8254078c5384a0"],"date_from":"2024-04-03"}},"CARDS":{"957e6f63546f3fecacce80192b6f7436496dc057":{}}}
add_pdf_from_uuids: >-
20966426721d0885ef9d4b95535e1d3198936f16,8772d6c978d37d7af83094abf380b8b703e94105
x-codeSamples:
- lang: cURL
label: CLI
source: |
curl -X POST 'https://api.wealthreader.com/entities/' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d 'api_key=a1b2c3d4e5f6g7h8i9j0' \
-d 'code=caixabank' \
-d 'token=MOCKDATA' \
-d 'product_types=accounts,portfolios' \
-d 'only_balances=false' \
-d 'date_from=2024-01-01' \
-d 'date_to=2025-12-31' \
-d 'required_products_schema={"ACCOUNTS":{"0ae4d722b1c82feeafb4b36b2893230444071335":{"only_balances":false,"add_pdf_from_uuids":["90763109952d4f2ebece8dceca8254078c5384a0"],"date_from":"2024-04-03"}},"CARDS":{"957e6f63546f3fecacce80192b6f7436496dc057":{}}}' \
-d 'add_pdf_from_uuids=20966426721d0885ef9d4b95535e1d3198936f16,8772d6c978d37d7af83094abf380b8b703e94105'
responses:
'200':
description: data obtained from the entity
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/entity-data'
'400':
description: error
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/error'
get:
tags:
- Advanced
x-internal: true
summary: Retrieves the list of supported entities
description: >
This endpoint is optional and not required for standard integrations.
Use only if explicitly instructed by Wealth Reader.
Retrieves the list of supported entities and the information needed to
draw the entity's login form.
operationId: getEntities
parameters:
- name: show_only_tested
in: query
description: >-
Indicates whether to show only tested entities. Default value is 0.
In production environments, always use 1.
required: false
schema:
type: integer
enum:
- 0
- 1
default: 0
responses:
'200':
description: list of entities
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/entities'
'400':
description: error
content:
application/json:
schema:
$ref: '#/components/schemas/error'
/entities/category-types/:
get:
tags:
- Core
summary: List of transaction types
parameters:
- name: lang
in: query
description: Response language
required: false
schema:
type: string
default: es
enum:
- es
- en
responses:
'200':
description: Category types with their description
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/category-types'
'400':
description: error
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/error'
/tokens/:
post:
tags:
- Core
summary: Query tokens associated with an api_key
description: >-
Use this method to query all tokens linked to a specific api_key.
Results are returned in blocks of 500 tokens per page.
operationId: queryTokensByApiKey
requestBody:
required: true
content:
application/x-www-form-urlencoded:
schema:
type: object
properties:
api_key:
type: string
description: api_key to identify the client in the service
example: a1b2c3d4e5f6g7h8i9j0
page:
type: number
description: >-
Specify the **page number** you want to retrieve. Each page
contains up to 500 tokens. If not provided, the default
value is `1`.
example: 2
example:
api_key: a1b2c3d4e5f6g7h8i9j0
page: 1
responses:
'200':
description: List of tokens associated with the provided api_key
content:
application/json:
schema:
type: array
items:
type: object
properties:
token:
type: string
description: Token
entity_code:
type: string
description: Entity code of the token
created_at:
type: string
format: date-time
description: Token creation date
accesed_at:
type: string
format: date-time
description: Last access date of the token
times_accesed:
type: integer
description: Number of times the token has been accessed
latest_code:
type: integer
description: Most recent response code
latest_session:
type: string
description: >-
ID of the last session associated with the token in
hexadecimal format
'400':
description: Bad request, invalid parameters
content:
application/json:
schema:
$ref: '#/components/schemas/error'
'401':
description: Unauthorized, incorrect api_key
content:
application/json:
schema:
$ref: '#/components/schemas/error'
'500':
description: Internal server error
content:
application/json:
schema:
$ref: '#/components/schemas/error'
/tokens/revoke/:
post:
tags:
- Core
summary: Revoke a token
description: >-
This method allows revoking an existing token to disauthorize future API
access requests.
operationId: revokeToken
requestBody:
required: true
content:
application/x-www-form-urlencoded:
schema:
type: object
properties:
api_key:
type: string
description: Identifies the client in the service
token:
type: string
description: Token to be revoked.
responses:
'200':
description: Token successfully revoked
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: true
message:
type: string
example: Token successfully revoked.
'400':
description: Bad request, invalid parameters
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/error'
'401':
description: Unauthorized, invalid token or already revoked
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/error'
'500':
description: Internal server error
content:
application/json:
schema:
$ref: '#/components/schemas/error'
/tokens/reasign/:
post:
tags:
- Core
summary: Reassign a token to a different api_key
description: This method allows reassigning a token from one api_key to another.
operationId: reasignToken
requestBody:
required: true
content:
application/x-www-form-urlencoded:
schema:
type: object
properties:
api_key_source:
type: string
description: api_key from which to reassign the token.
example: a1b2c3d4e5f6g7h8i9j0
api_key_target:
type: string
description: api_key to which to reassign the token.
example: b2c3d4e5f6g7h8i9j0k1
token:
type: string
description: Token to be reassigned.
example: FRJ0mHlaqZwLzu
example:
api_key_source: a1b2c3d4e5f6g7h8i9j0
api_key_target: b2c3d4e5f6g7h8i9j0k1
token: FRJ0mHlaqZwLzu
responses:
'200':
description: Token successfully reassigned
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: true
message:
type: string
example: Token successfully reassigned.
'400':
description: Bad request, invalid parameters
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/error'
'401':
description: Unauthorized, incorrect api_key
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/error'
'500':
description: Internal server error
content:
application/json:
schema:
$ref: '#/components/schemas/error'
/domains/:
post:
tags:
- Core
summary: Add a new domain
description: >-
Adds the association between the domain that will host the widget and
the destination webhook. To edit or test your domains, use
https://www.wealthreader.com/clients/
operationId: addDomain
requestBody:
required: true
content:
application/x-www-form-urlencoded:
schema:
type: object
properties:
method:
type: string
description: Method to execute.
example: add
api_key:
type: string
description: User's API key.
example: a1b2c3d4e5f6g7h8i9j0
domain:
type: string
description: Domain to add.
example: http://desarrollo.cliente.es
url_callback:
type: string
description: URL for callback.
example: https://desarrollo.cliente.es/hooks/wealthreader
tokenize:
type: string
enum:
- '1'
- '0'
description: >
Controls whether the widget initiates a tokenization flow:
* `1` - The user authenticates with the financial
institution (login, consent, 2FA if required) and a reusable
token is returned for future queries
* `0` - No tokenization is performed. The previously
obtained token value must be included in the request
example: '1'
required:
- method
- api_key
- domain
- url_callback
- tokenize
example:
method: add
api_key: a1b2c3d4e5f6g7h8i9j0
domain: https://www.cliente.com
url_callback: https://www.cliente.com/webhooks/wealthreader
tokenize: '1'
responses:
'200':
description: Domain successfully added
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
message:
type: string
'400':
description: Bad request, invalid parameters
'401':
description: Unauthorized, incorrect API key
'500':
description: Internal server error
/error-codes/:
get:
tags:
- Core
summary: List of error codes
description: >
List of error codes. Pay special attention to the fact that not all
error codes should receive the same treatment from your application. For
an incorrect password error, you should not retry the call with the same
parameters, but for an error indicating that the entity is under
maintenance, you can retry. Request a technical session with our team to
resolve any questions about error management.
parameters:
- name: lang
in: query
description: Response language
required: false
schema:
type: string
default: es
enum:
- es
- en
responses:
'200':
description: >-
Error codes with their description, possible cause, and how to
proceed
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/warning-error-codes'
'400':
description: error
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/error'
/warning-codes/:
get:
tags:
- Core
summary: List of warning codes
description: |
List of warning codes.
parameters:
- name: lang
in: query
description: Response language
required: false
schema:
type: string
default: es
enum:
- es
- en
responses:
'200':
description: >-
Error codes with their description, possible cause, and how to
proceed
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/warning-error-codes'
'400':
description: error
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/error'
/verify/iban-ownership/:
post:
tags:
- Advanced
x-internal: true
summary: Verify bank account ownership via IBAN
description: >
This endpoint is optional and not required for standard integrations.
Use only if explicitly instructed by Wealth Reader.
Allows verifying whether a natural or legal person is the holder of a
specific bank account using the IBAN and the identification data of the
alleged holder.
It requires an api_key with the IBAN_OWNERSHIP product authorized.
The initial request is sent with api_key, iban, document_type,
document_number and holder_name. If the result returns status PENDING,
the verification can be queried again by sending only api_key and
session. NO_RESPONSE is a final error result: to retry, a new
verification must be started without session.
requestBody:
required: true
content:
application/x-www-form-urlencoded:
schema:
oneOf:
- title: Initial verification
type: object
required:
- api_key
- iban
- document_type
- document_number
- holder_name
properties:
api_key:
type: string
description: >-
Identifies the client in the service. It must have the
IBAN_OWNERSHIP product authorized.
iban:
type: string
description: IBAN code of the bank account to verify (without spaces)
example: ES4914651234561234567890
document_type:
type: string
description: Type of identification document
enum:
- NIF
- NIE
- Pasaporte
- CIF
example: NIF
document_number:
type: string
description: Identification document number
example: 12345678Z
holder_name:
type: string
description: Full name of the natural person or company name
example: LUIS GARCIA BAQUERO
- title: Follow-up query for a PENDING verification
type: object
required:
- api_key
- session
properties:
api_key:
type: string
description: >-
Identifies the client in the service. It must have the
IBAN_OWNERSHIP product authorized.
session:
type: string
description: >-
Identifier returned in `statistics.SESSION` by a
previous verification whose status was PENDING. Only
PENDING sessions can be reused; an already finished,
invalid or non-existent session returns an error. When
`session` is sent, no other parameter besides `api_key`
is needed.
example: 0123456789abcdef
examples:
initialVerification:
summary: Initial verification
value:
api_key: a1b2c3d4e5f6g7h8i9j0
iban: ES4914651234561234567890
document_type: NIF
document_number: 12345678Z
holder_name: LUIS GARCIA BAQUERO
pendingFollowUp:
summary: Follow-up query for a PENDING verification
value:
api_key: a1b2c3d4e5f6g7h8i9j0
session: 0123456789abcdef
responses:
'200':
description: Verification result
content:
application/json:
schema:
type: object
required:
- success
- payload
- statistics
properties:
success:
type: boolean
example: true
payload:
type: object
required:
- iban_ownership
properties:
iban_ownership:
type: object
required:
- ownership
- status
- result
properties:
ownership:
type: boolean
nullable: true
description: >-
`true` when ownership is confirmed, `false` when
it is rejected and `null` while the verification
is still PENDING.
example: true
status:
type: string
enum:
- CONFIRMED
- REJECTED
- PENDING
description: >-
Verification status. CONFIRMED: ownership
confirmed. REJECTED: the IBAN does not belong to
the indicated holder. PENDING: the verification is
still being processed and can be queried again by
sending `session`.
example: CONFIRMED
result:
type: string
description: Descriptive message of the result
example: La titularidad del IBAN ha sido confirmada.
statistics:
$ref: '#/components/schemas/statistics'
examples:
confirmed:
summary: 'CONFIRMED: ownership confirmed'
value:
success: true
payload:
iban_ownership:
ownership: true
status: CONFIRMED
result: La titularidad del IBAN ha sido confirmada.
statistics:
SESSION: 0123456789abcdef
execution_time: 0.123
warnings: []
rejected:
summary: 'REJECTED: the IBAN does not belong to the holder'
value:
success: true
payload:
iban_ownership:
ownership: false
status: REJECTED
result: El IBAN no pertenece al titular indicado.
statistics:
SESSION: 0123456789abcdef
execution_time: 0.123
warnings: []
pending:
summary: 'PENDING: query again sending session'
value:
success: true
payload:
iban_ownership:
ownership: null
status: PENDING
result: La verificación de titularidad está pendiente.
statistics:
SESSION: 0123456789abcdef
execution_time: 0.123
warnings: []
'400':
description: Request error
content:
application/json:
schema:
type: object
required:
- success
- error
- payload
- statistics
properties:
success:
type: boolean
example: false
error:
$ref: '#/components/schemas/error-detail'
payload:
type: array
description: Always an empty array in error responses
items: {}
statistics:
$ref: '#/components/schemas/statistics'
examples:
noResponse:
summary: >-
NO_RESPONSE: final error, start a new verification without
session
value:
success: false
error:
code: 3001
message: >-
BBVA no obtuvo respuesta de la entidad destinataria.
Inicie una nueva verificación sin session.
payload: []
statistics:
SESSION: 0123456789abcdef
execution_time: 0.123
warnings: []
/user/register/:
post:
tags:
- Advanced
x-internal: true
summary: Register a new user
description: >
This endpoint is optional and not required for standard integrations.
Use only if explicitly instructed by Wealth Reader.
This endpoint allows registering a user either on the portfolio transfer
platform, Easytransfer, or on the reporting tool, Acumulas, based on a
unique identifier.
operationId: registerUser
requestBody:
required: true
content:
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/register-user-request'
responses:
'200':
description: User registered successfully
content:
application/json:
schema:
$ref: '#/components/schemas/register-user-response'
'400':
description: Bad request (e.g., missing required fields)
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
'401':
description: Invalid API key
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/user/check/:
post:
tags:
- Advanced
x-internal: true
summary: Check user registration status
description: >
This endpoint is optional and not required for standard integrations.
Use only if explicitly instructed by Wealth Reader.
Checks if a user is registered in the Easytransfer or Acumulas system
and returns the unique access link for the user.
operationId: checkUser
requestBody:
required: true
content:
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/check-user-request'
responses:
'200':
description: User status returned successfully
content:
application/json:
schema:
$ref: '#/components/schemas/check-user-response'
'400':
description: Bad request
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
'401':
description: Invalid API key
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/user/revoke/:
post:
tags:
- Advanced
x-internal: true
summary: Revoke a previously registered user
description: >
This endpoint is optional and not required for standard integrations.
Use only if explicitly instructed by Wealth Reader.
This endpoint allows unregistering a user from the Easytransfer or
Acumulas platform service.
operationId: revokeUser
requestBody:
required: true
content:
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/revoke-user-request'
responses:
'200':
description: User unregistered successfully
content:
application/json:
schema:
$ref: '#/components/schemas/revoke-user-response'
'400':
description: Bad request (e.g., missing required fields)
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
'401':
description: Invalid API key
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/batch/load/:
post:
tags:
- Advanced
x-internal: true
summary: Batch connection loading
description: >
This endpoint is optional and not required for standard integrations.
Use only if explicitly instructed by Wealth Reader.