API Reference
The Integry API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded and form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
Setting Up
Base URL
Authentication
The Integry API requires an App-Key
, User-ID
and a hash of App-Secret
and User-ID
in the request headers to authenticate requests.
You can view and copy your App-Key
and App-Secret
from the Integry app.
User-ID
is a unique string identifier for a user in your app. Function Calls and Integrations are associated to a user ID.
If your app has workspaces/accounts and you want integrations to be shared across all users in a workspace/account, use the workspace/account ID as the user ID.
Calculating the hash
Calculate the hash server-side using HMAC SHA256.
Headers
Pass the App-Key
, computed hash and User-ID
in the headers of the API call.
Apps
List all apps
GET
/apps
List all apps available in Integry. If you need more, please reach out!
Query parameters
Response
Get an app
GET
/apps/<app_name>
Get the details of an individual app by passing <app_name>
as a path variable.
Response
Functions
List all functions
GET
/functions
List all functions available in Integry. If you need more, make a passthrough request or reach out!
Query Parameters
Response
Get a function
GET
/functions/<function_name>
Get the JSON schema of an individual function by passing function name as a path variable.
Query Parameters
Response
All supported function parameters
are returned as keys, along with their type
and description
as key, value pairs. Required parameters are listed in the required
array.
Sample response for pipedrive-add-a-person
get function call:
Call a function
POST
/functions/<function_name>/
Call a function by passing <function_name>
as a path variable and the function parameters in the request body. Integry will automatically add the user's authentication credentials (eg. access token, API key) to the call.
Query Parameters
Integry will execute the function if the user has already connected their account for the function app, and all required parameters (if any) are provided in the body. These function calls will show in the Function Calls log in the Integry app.
Integry will not execute the function if the user has not connected an account, or the parameters passed are invalid. These function calls will not show in the Function Calls log.
Body
Pass the function parameters in the request body.
Sample body for pipedrive-add-a-person
function call:
Sample body for pipedrive-get-all-persons
function call with next_page
:
Response
If Integry executes the function, it will respond with a 200 OK
with following keys in the response body:
network_code
: HTTP response status code of the onwards API call made by Integry.output
: HTTP response body of the onwards API call made by Integry.next_page
: The cursor for the next page. It will only be present in responses of functions that support paginated calls. If there are no more pages, it will be empty.
If Integry does not execute the function, it will respond with a 400 Bad Request
with following keys in the response body:
error
: Summary of the error.error_details[]
: Detailed errors for individual fields (if applicable).
Sample responses for pipedrive-add-a-person
and pipedrive-get-all-persons
:
In rare cases where Integry is unable to determine if there are more pages, it will respond with a next_page
cursor. Your subsequent call will return an empty output[]
and next_page
cursor since there are no more pages.
Last updated