A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

​
A

A unique string returned as part of the connection process. For security reasons, it is required to be able to call any Job under that connection.
Autonomous component that executes tasks under a predefined structure. It can interact with external systems, APIs, or websites.
Essential identifiers to be able to connect to sources and use Jobs through our API.
More information here.

​
C

One of the two required authentication keys, the other being secret.
You need both of these in the headers of each of your API calls for the system to recognize you as our client.

​
D

Main UI to visually interact with our API and create the Jobs you need to achieve your goal.
You can access it here.

​
J

A granular unit of work inside a session. Besides a few exceptions, all Jobs are actions (either read or write) that can be made on data while authenticated under valid credentials.
More details.
A unique string that links to a specific Job. To call a Job, it is essential to specify which one via this job_code.
A unique string that is sent via webhook after calling a Job. It allows for a quick identification of a Job.

​
K

Essential identifiers to be able to connect to sources and use Jobs through our API.
More information here.

​
L

One of our two environments you can use, the other being Sandbox.
The Live environment interacts with actual data. More information here.

​
S

One of our two environments you can use, the other being Live.
Sandbox can do everything our Live environment can do, for free. However, it is essentially a testing ground, as webhook responses will come with mock data. More information here.
One of the two required authentication keys, the other being client ID.
You need both of these in the headers of each of your API calls for the system to recognize you as our client.
Any portal that can be accessed online, which hosts the data with which you want to interact.
A unique string that identifies a source.

​
W

A webhook is a way for one application to send real-time information to another application via an HTTP request, triggered automatically when a specific event happens. More information about our webhooks here.
Small UI that can be integrated into apps and website that gives users an intuitive UI to pass their credentials through. More information about our webhooks here.