The Synqly Management APIs enable you to manage the resources within your Synqly organization, such as setting up Accounts for your customers and creating Integrations to connect your product to the different service Providers supported by Synqly.
For more information see the Synqly Overview.
Accounts under your Organization are used to manage Integrations, Credentials, and other account specific resources. Accounts are secure containers and may be used to represent tenants in your system. Data is never shared across accounts.
For more information on Accounts, see the Synqly Overview.
An Integration Point describes a class of Integrations, and lets you describe names, allowed providers and other configuration that should apply to integrations associated with the Integration Point.
While an Integration can be created without associating it with an Integration Point, some Synqly features require the use of Integration Points, such as:
Integration Points belong to the Organization, and can be associated with Integrations belonging to different Accounts.
For more information on Integration Points, see the Synqly Overview.
An Integration represents the connection to a specific Provider. Once configured, an Integration enables interaction with the target Provider via our unified and normalized Connector APIs.
Each Integration belongs to an Account and may be associated with an Integration Point to provide additional features and configuration.
For more information on Integrations, see the Synqly Overview.
Select a field to order the results by. Defaults to name. To control the direction of the sorting, append [asc] or [desc] to the field name. For example, name[desc] will sort the results by name in descending order. The ordering defaults to asc if not specified. May be used multiple times to order by multiple fields, and the ordering is applied in the order the fields are specified.
curl -i -X GET \
'https://api.synqly.com/v1/members?filter=string&limit=0&order=string&start_after=string' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'{ "result": [ { … } ] }
Email name to use for this Member. Also used for duplicate detection and default sort order.
Member secret used to logon. Must be at least 8 characters long and fewer than 72 characters. There are no restrictions on the characters used; however, the secret must be sufficiently complex. It cannot be a common word, previously leaked password, or easily guessed sequences like qwerty or 12345.
Optional member time-to-live duration. After a member expires, system requires a change password to re-enable member. Minimum 1 day, Maximum 1 year, Default 180 days.
Options: "expired" will force change password on first logon.
User's full display name. Defaults to the same value as the 'name' field if not specified.
curl -i -X POST \
https://api.synqly.com/v1/members \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"name": "string",
"fullname": "string",
"nickname": "string",
"picture": "string",
"secret": "string",
"role_binding": [
"string"
],
"options": {
"ttl": "string",
"options": [
"disabled"
],
"token_ttl": "string"
}
}'{ "result": { "member": { … } } }
curl -i -X GET \
'https://api.synqly.com/v1/members/{memberId}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'{ "result": { "id": "string", "state": "disabled", "last_logon": "2019-08-24T14:15:22Z", "fullname": "string", "nickname": "string", "picture": "string", "ttl": "string", "token_ttl": "string", "expires": "2019-08-24T14:15:22Z", "pin_expires": "2019-08-24T14:15:22Z", "role_binding": [ … ], "name": "string", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z" } }
curl -i -X PUT \
'https://api.synqly.com/v1/members/{memberId}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"id": "string",
"state": "disabled",
"last_logon": "2019-08-24T14:15:22Z",
"fullname": "string",
"nickname": "string",
"picture": "string",
"ttl": "string",
"token_ttl": "string",
"expires": "2019-08-24T14:15:22Z",
"pin_expires": "2019-08-24T14:15:22Z",
"role_binding": [
"string"
],
"name": "string",
"created_at": "2019-08-24T14:15:22Z",
"updated_at": "2019-08-24T14:15:22Z"
}'{ "result": { "id": "string", "state": "disabled", "last_logon": "2019-08-24T14:15:22Z", "fullname": "string", "nickname": "string", "picture": "string", "ttl": "string", "token_ttl": "string", "expires": "2019-08-24T14:15:22Z", "pin_expires": "2019-08-24T14:15:22Z", "role_binding": [ … ], "name": "string", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z" } }
The path to the field to copy from. This is required for copy and move operations.
The value to set the field to. This is required for add, replace and test operations.
curl -i -X PATCH \
'https://api.synqly.com/v1/members/{memberId}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '[
{
"op": "add",
"path": "string",
"from": "string",
"value": null
}
]'{ "result": { "id": "string", "state": "disabled", "last_logon": "2019-08-24T14:15:22Z", "fullname": "string", "nickname": "string", "picture": "string", "ttl": "string", "token_ttl": "string", "expires": "2019-08-24T14:15:22Z", "pin_expires": "2019-08-24T14:15:22Z", "role_binding": [ … ], "name": "string", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z" } }
curl -i -X DELETE \
'https://api.synqly.com/v1/members/{memberId}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'