Skip to content

Overview

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.

Authentication

You can obtain a LinkCy Authorization Key by contacting our commercial team here.

Download OpenAPI description
Languages
Servers
Generated server url
https://api.sandbox.linkcy.cloud/
Operations
Operations
Operations
Operations
Operations

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
Operations
Operations

Send phone verification code by sms

Request

This Endpoint allows you to send a verification code to your user by SMS. This code is a 6-digit code.

If you want to personalize the Sender Name, please contact your customer care.

NOTE : In Sandbox, no SMS is sent. Verification code will always be 123456

Security
Linkcy-Auth
Bodyapplication/jsonrequired
Any of:
consumerIdstring(uuid)

Id of the consumer verifying.

Mandatory if not authenticated as consumer.

application/json
{ "consumerId": "9e675a24-20d6-4913-9836-f861cd23e89e" }

Responses

Message sent

Bodyapplication/json
ttlstringrequired

The phone verification code time to live duration in ISO 8601.

Default "PT10M"
Response
application/json
{ "ttl": "PT10M" }

Send an email verification link by email

Request

This Endpoint allows you to send an email verification to your user. The user will receive a link by email in order to verify his current email.

Security
Linkcy-Auth
Bodyapplication/jsonrequired
Any of:
consumerIdstring(uuid)

Id of the consumer verifying its email (Will be ignored and deducted from current authenticated user if end-user).

emailSubjectstring[ 0 .. 255 ] characters

Subject of the verification email, by default is '[{partnerName}] Please verify your email address'.

Example: "[{partnerName}] Please verify your email"
urlOnSuccessstring

Redirect url on email verified.

Example: "https://google.com"
urlOnFailurestring

Redirect url on email verification failed.

Example: "https://google.com"
application/json
{ "consumerId": "9e675a24-20d6-4913-9836-f861cd23e89e", "emailSubject": "[{partnerName}] Please verify your email", "urlOnSuccess": "https://google.com", "urlOnFailure": "https://google.com" }

Responses

Verification email sent

Bodyapplication/json
ttlstringrequired

The email verification link time to live duration in ISO 8601.

Default "PT48H"
Response
application/json
{ "ttl": "PT48H" }

Request

This endpoint allows you to verify an end-user's address using different methods:

  • LINK: This method generates a URL link that the end-user can use to complete its Proof of Address (POA).

  • UPLOADED_DOCUMENT: Use this method when a POA document has already been uploaded which will be used to verify the address.

  • DELEGATED: When the address verification is delegated to the partner (property "delegatedPoa" set to "true") and the POA document has been uploaded, you can use this method to update the address status to "VERIFIED".

Security
Linkcy-Auth
Bodyapplication/jsonrequired
One of:
typestringrequired
Value"LINK"
addressIdstring(uuid)required
ttlstringrequired

Time-to-live (TTL) duration before the link expires .

Supports ISO 8601 duration format (e.g., 'PT1800S' for 1800 seconds, 'PT5M' for 5 minutes, 'P7D' for 7 days).

Example: "PT8H6M12.345S"
application/json
{ "type": "LINK", "addressId": "785d1fc4-8ab5-48f1-8685-117cac9865d6", "ttl": "PT8H6M12.345S" }

Responses

OK

Bodyapplication/json
urlstringrequired
ttlstringrequired
Example: "PT8H6M12.345S"
Response
application/json
{ "url": "string", "ttl": "PT8H6M12.345S" }
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations