Core Concepts


Integration Provider

An integration provider is a 3rd party app which your end users connect to, such as Hubspot or Salesforce.


A schema represents a certain data resource you want to work with. For example, if your company is in sales or marketing, you might want a schema for CRM contact data and a schema for CRM company data.

Schemas can typically be identified through their endgrate_type: a unique keyword such as crm-contact or crm-company that encapsulates a given resource class.

Learn more about schemas and how to define them here.


A session represents the connection between your end user and an integration provider. For example, a session could be a certain user's connection to HubSpot, or another user's connection to Salesforce.


A transfer is an action taken for a given session. For example, a transfer might be pulling in CRM contact data, or pushing out CRM company data.

Integration Flow

When working with Endgrate, the integration flow usually consists of the following steps:

  1. Initiate a session with some schemas that you want to work with.
  2. Redirect your end user to Endgrate. The end user chooses an integration provider and authenticates.
  3. Trigger transfers to pull, push, and sync data between your product and your end user's selected integration provider.

What’s Next