POST
/
integrations
/
{integration_id}
/
relink
Create reconnection link
curl --request POST \
  --url https://api.kombo.dev/v1/integrations/{integration_id}/relink \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "language": "en",
  "scope_config_id": "9Pv6aCFwNDEzPNmwjSsY9SQx",
  "link_type": "EMBEDDED"
}'
{
  "status": "<string>",
  "data": {
    "link": "<string>"
  }
}
Embed this the same way you would embed the connect link. By default, the link will be valid for 1 hour.

​
Example Request Body

{
  "language": "en",
  "scope_config_id": "9Pv6aCFwNDEzPNmwjSsY9SQx",
  "link_type": "EMBEDDED"
}

Authorizations

​
Authorization
string
header
required

Create an API key on the Secrets page in the Kombo dashboard.

Path Parameters

​
integration_id
string
required

POST /integrations/:integration_id/relink Parameter

Body

application/json

POST /integrations/:integration_id/relink Request body

​
language
enum<string> | null
default:en

Language of the connection flow UI.

Available options:
en,
de,
fr,
it,
es
​
scope_config_id
string | null

Specify a scope config which the integration will start using once the reconnection flow has been completed.

This can be useful if you want to update the permissions of an integration, but only want the change to take effect once the user has updated their API credentials to prevent sync issues.

​
link_type
enum<string>
default:EMBEDDED

The type of link you want to create. EMBEDDED is for the embedded flow using the Kombo Connect SDK (these links are valid for 1 hour) and MAGIC_LINK is for magic links which you send out manually to customers (there are valid for 1 year).

This defaults to EMBEDDED, which is our recommended method of implementing the connection flow for a seamless user experience.

Available options:
EMBEDDED,
MAGIC_LINK

Response

POST /integrations/:integration_id/relink Positive response

​
status
string
required
Allowed value: "success"
​
data
object
required