The id of the end-user, can be a consumer or corporate. Mandatory if not authenticated as end-user.
- Get Information on a Crypto Beneficiary
List Crypto Beneficiaries
Add a new crypto-beneficiary
Update information of a Crypto Beneficiary
Get Information on a Cryp...
Linkcy Api (1.114.5)
This is the partner API from linkcy. Here you can find our API documentation.
LinkCy API allows you to create fully embedded banking products for your own company or consumers. This API is backed by all mandatory requirements by financial authorities. To process, information provided into the API must be accurate.
You can obtain a LinkCy Authorization Key by contacting our commercial team here.
Download OpenAPI description
Overview
Languages
Servers
Generated server url
https://api.sandbox.linkcy.cloud/
Consumer
The consumer represents the individual partner client. It must have a valid phone number and be formally identified with a KYC procedure before carrying out any operation.
Operations
Headers
Bodyapplication/jsonrequiredThe strategy to use when a SCA is required:
More information:
PUSH_NOTIFICATION: will send a notification if the SCA is required.DATA_SIGNING: Linkcy-SCA-Signature header must contain signature provided by PowerAuth Mobile SDK on registered device.BY_PASS: Sandbox only - will ignore any SCA if used.
Error Codes
- 409 Conflict
SCA_REQUIRED: The operation you are trying to do requires SCA, current strategy {0}.
Default PUSH_NOTIFICATION
Enum"PUSH_NOTIFICATION""DATA_SIGNING""BY_PASS"
The signature that needs to be validated, it is generated from data signing.
More information:
- Signature will be verified against wultra.
- Operation will be denied if signature is not valide.
- Avoid creating multiple signature at same time for the same registration.
- Signature TTL is 30 sec.
Error Codes
- 401 Forbidden
SCA_SIGNATURE_DOES_NOT_MATCH: The sca signature provided doesn't match the one required for this operation
- 404 Not Found
NO_ACTIVE_SCA_DEVICE_FOUND: No active SCA device could be found.
- 409 Conflict
SCA_DEVICE_NOT_VALID: The device cannot be used to sign this data.SCA_SIGNATURE_FORMAT_INVALID: The signature format for data signing SCA strategy is invalid: HTTP header validation failed.SCA_SIGNATURE_MISSING: The signature required for data signing SCA strategy is missing.
- 500 Internal Server Error
SCA_UNEXPECTED_ERROR: Unable to perform SCA operation
Complete name of the person (firstName middleName lastName) or name of the company.
Counterparty wallet blockchain. The enumeration is the same as the one in Create Wallet endpoint because you can only create transactions on the same blockchain as the wallet sender.
Enum"BITCOIN""ETHEREUM""BNB_SMART_CHAIN"
- Generated server urlhttps://api.sandbox.linkcy.cloud/api/partner/crypto/beneficiaries
- Payload
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
application/json
{ "endUserId": "120e9d1f-8444-4b91-85e8-5b208615a3e5", "type": "PERSON", "name": "string", "friendlyName": "string", "display": true, "walletDetails": { "address": "string", "blockchain": "BITCOIN", "type": "CUSTODIAL", "provider": "string" } }
Response
application/json
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08" }
If you notice an error or find something unclear, we’d greatly appreciate your feedback to help us improve.
- Generated server urlhttps://api.sandbox.linkcy.cloud/api/partner/crypto/beneficiaries/{cryptoBeneficiaryId}
- Payload
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
No request payloadResponse
application/json
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "friendlyName": "string", "type": "PERSON", "creationDate": "2019-08-24T14:15:22Z", "updateDate": "2019-08-24T14:15:22Z", "active": true, "display": true, "status": "DECLINED", "walletDetails": { "address": "string", "blockchain": "BITCOIN", "type": "CUSTODIAL", "provider": "string" } }
If you notice an error or find something unclear, we’d greatly appreciate your feedback to help us improve.
- Generated server urlhttps://api.sandbox.linkcy.cloud/api/partner/crypto/beneficiaries/{cryptoBeneficiaryId}
- Payload
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
application/json
{ "active": true, "display": true, "friendlyName": "string", "name": "string", "status": "DECLINED" }
Response
application/json
{ "cryptoBeneficiaryId": "348139d3-780c-4a44-9242-2411d3b41501" }