Introduction
In this guide, you will use the Cyclr API to call a connector method. Cyclr will act as a proxy and pass your request to the external application.
Before you start, make sure you have created an end user account and authenticated a connector.
Get Account Connectors
Let’s get a list of installed account connectors from your account so Cyclr knows which account connector you want to make the request with.
Request:
GET https://yourCyclrInstance/v1.0/account/connectors
Authorization: Bearer ****************************************************************
X-Cyclr-Account: 00000000-0000-0000-0000-000000000000
Response:
[
{
"Id": 123,
"Name": "Salesforce Account 1",
"Description": "",
"Connector": {
"Id": 1,
"Name": "Salesforce"
}
},
{
"Id": 456,
"Name": "Salesforce Account 2",
"Description": "",
"Connector": {
"Id": 1,
"Name": "Salesforce"
}
}
]
In the response, 123 is an account connector ID. 1 is the ID for the underlying connector.
Identify the Connector Method to Call
Each Connector Method in Cyclr has a MethodUniqueIdentifier value. You can get a list of Methods with their unique identifiers using the 2 endpoints below.
(use the first endpoint for Connectors that don’t have a “Version” property)
GET https://yourCyclrInstance/v1.0/connectors/{name}/methods
GET https://yourCyclrInstance/v1.0/connectors/{name}/{version}/methods
Response:
[
{
"Id": 116,
"Name": "Update Ticket",
"Description": "Updates a ticket.",
"EndPoint": "https://api.example/updateTicket",
"MethodUniqueIdentifier": "8f8df8ef-3007-11e7-a033-06abe76375dd"
},
{
"Id": 117,
"Name": "Delete Ticket",
"Description": "Deletes a ticket.",
"EndPoint": "https://api.example/deleteTicket",
"MethodUniqueIdentifier": "56d8a7ef-3457-af37-a3fd-0645386a75bd"
}
]
Call a Connector Method
You can now call a connector method and get the raw response from the third-party application.
Request
POST https://yourCyclrInstance/v1.0/account/connectors/{account connector ID}/methods/{method ID}
Authorization: Bearer ****************************************************************
Content-Type: application/json
X-Cyclr-Account: 00000000-0000-0000-0000-000000000000
{}
Response
{
"records": [{
"Id": "1001",
"FirstName": "John",
"LastName": "Smith",
"Name": "John Smith",
"Email": "johnsmith@example.com"
},
{
"Id": "1002",
"FirstName": "Jane",
"LastName": "Doe",
"Name": "Jane Doe",
"Email": "janedoe@example.com"
}
]
}
Call a Connector Method with Parameters
If the method you are calling requires any values to be passed, they must be included in your Request Body as follows:
Request
POST https://yourCyclrInstance/v1.0/account/connectors/{account connector ID}/methods/{method ID}
Authorization: Bearer ****************************************************************
Content-Type: application/json
X-Cyclr-Account: 00000000-0000-0000-0000-000000000000
{
"Parameters": {
"400123": "true"
},
"Fields": {
"500123": "test@example.com"
}
}
IP Restriction
Access to Cyclr APIs used for passing requests to external applications is restricted by IP. The IP restricted APIs are as follows:
- GET /v1.0/account/connectors/{id}/methods/{methodId} Calls a connector method
- POST /v1.0/account/connectors/{id}/methods/{methodId} Calls a connector method
- GET /v1.0/account/connectors/{id}/test/{methodId} Tests a connector method
- POST /v1.0/account/connectors/{id}/test/{methodId} Tests a connector method
If you are using Cyclr APIs to call standard connectors, i.e. third-party connectors that are not native to your application, the Cyclr API request can only be made from a list of IP addresses approved by us.
Native connectors with the IsPartnerIntegrationConnector flag set to true can be called from any IP addresses.
If you would like to use Cyclr APIs to call standard connectors, please contact our support team to whitelist your IP.
Edit me