Locoia
Search…
Create Connector Authentication
Create Connector authentication in your own SaaS product for dynamic insight Connectors.
To integrate Connector authentication in your own SaaS product as part of a multi-tenant flow, follow the below steps.

Create authentication

1
{
2
"connector_id": "some uuid4 of the corresponding connector",
3
"name": "Test Name",
4
"auth_type": "username_password",
5
"auth_token": "",
6
"auth_details": "",
7
"api_endpoint": "sftp://user:[email protected]_ip/path",
8
"user_input": {},
9
"username": "user123",
10
"password": "password123",
11
"tags": [
12
"Example Tag",
13
"Customer XYZ"
14
]
15
}
Copied!
The uuid4 can be received by making a GET against the connector /v1/connectors?filter=name,like,%22%25ft%25%22 where `ftp` is the connector name.
To use this authentication in a white label flow, pass it's uuid4 you receive in the response as part of the query string as per the example here. So ideally, after creating, you store it on your customer's account or company object in order to use it for all automation flows.

Update authentication

To update, PUT /v1/connector-auths/**uuid4**
1
{
2
"connector_id":"some uuid4 of the corresponding connector",
3
"name":"Test Name",
4
"auth_type":"username_password",
5
"api_endpoint":"sftp://user:[email protected]_ip/path",
6
"username":"user123",
7
"password":"password123"
8
}
Copied!

Get authentication information

To list all auth, To update, PUT /v1/connector-auths/
To GET one: /v1/connector-auths/**uuid4**

Delete authentication

DELETE: /v1/connector-auths/**uuid4**

Limiting access via permissions

You can easily limit the permissions of connector auth e.g. for only one user to be visible in order make storing most secure.
Last modified 4mo ago