This article explains how integrator.io counts entitlements, particularly endpoints, so you can monitor your subscription usage and avoid unexpected overages.
Your account is allowed a specific number of entitlements, including flows run, endpoints invoked, on-premise agents used, and API calls, based on your Celigo platform subscription. It's a good practice to periodically monitor your entitlements to ensure that you're optimally using them.
An account owner or administrator can view a running total of these entitlements and the maximum values allowed in the account Subscription page. The Subscription page also enables you to view the usage details of all your entitlements in one place.
-
You must be an account owner or administrator.
Note
Usage data — including current and historical usage — is available on the 2024 Platform license only. If you're on the 2022 Endpoint license, usage data is not stored or displayed in integrator.io. To discuss upgrading your license, contact Celigo Support.
Endpoints are invoked:
-
when flows are run
-
when you trigger APIs: Learn more about tracking your API usage.
-
API usage depends on whether your call is direct or fully managed, and the type of API or resource you're calling. As a rule:
-
Only distinct endpoints invoked are counted. A detailed explanation of calculating endpoints is provided in the section below.
Endpoints are the connections your flows use to reach apps, databases, and universal services like HTTP and FTP. They are grouped into three categories: app connectors, databases, and universal connectors. When installing an Integration app or template, one of the first steps is to set up connections to applications. And when creating an export or import, you are always required to select the Application from any of the following three sections in the list:
-
Connectors, such as Acumatica and Salesforce, commonly referred to in Celigo documentation as "prebuilt" or "branded" connectors
Note
Connections to the Celigo integrator․io API are no longer counted as part of the endpoint entitlement calculation. Previously if your subscription was consuming all available endpoints, you could be prevented from certain operations that required special use of this endpoint (for example, cloning some templates and integration apps, and accessing flow errors via error APIs). Now that it is no longer counted, these issues will not occur.
-
Databases, such as MySQL and Snowflake, often called "data warehouses"
-
Universal connectors, such as FTP and HTTP, also known as "custom," "generic," or "technology services"
Endpoints are the sum of these three app connections.
Note
-
Webhooks are not considered endpoints because they are used to send an HTTP POST message over the web in real-time to an endpoint when an event occurs in an application, rather than as a destination for data.
-
Data loader flows are not considered while counting endpoints.
You are free to create as many connections to an app as you like. Multiple connections to the same app count as a single endpoint. This guideline applies to both production and sandbox environments. These connections increment your endpoint count when any of them is referenced in a flow that is run.
Your existing database connections count as one endpoint if they're hosted on the same host server. In these cases, only one endpoint is consumed, and you can connect to more databases without defining the database.schema.table in all queries. You only consume one endpoint if you connect to more than one dataset under the same projectId. This way, you won't go over the maximum number of endpoints when you create a new database connection on a single host server.
Any of the following changes to a host mid-month will result in a second endpoint being counted for the month:
-
Changing the domain (for example,
mysql.a.com→mysql.b.com) -
Switching between a domain name and an IP address, or vice versa
-
Changing the IP address to one in a different subnet (for example,
192.168.1.x→192.168.2.x)
Note
integrator.io counts a second endpoint only if you run a flow after making the change. Updating a connection's host without running a flow doesn't add to your endpoint count. Switching back to an endpoint already counted earlier in the month also doesn't add a new count.
Relational database management system (RDBMS): Multiple connections configured for the same RDBMS (except Google BigQuery) with the same host (domain or IP) count as a single endpoint.
Tip
For NetSuite Analytics Warehouse (NSAW), you can find the host name in the tnsnames.ora file.
Your existing Google BigQuery connections count endpoints by client email.
RDBMS
-
Google BigQuery (counted by client email, not host)
-
Oracle (DB (SQL), Autonomous Database, NSAW)
Non-relational database management system (non-RDBMS): For non-RDBMS, like DynamoDB, any connection configured to the same AWS Access Key ID counts as a single connection. Your connections are added to your endpoint app summary when any of them is referenced in a flow that is run.
Non-RDBMS
Text comparison determines how the Celigo platform identifies additional connections to the same endpoint:
-
GraphQL, HTTP, and REST API (of all auth types) – Multiple connections to one of these three options are counted as a single endpoint app as long as the Base URI is identical.
-
AS2 – Multiple connections configured for the same server (domain or IP) and port are counted as a single endpoint.
-
FTP (including SFTP and FTPS, internal or external) – Multiple connections configured for the same server (domain or IP) and port are counted as a single endpoint.
-
Wrapper – Each wrapper resource (essentially a custom connection to a server stack) used in a flow run is counted as a single endpoint.
For HTTP, REST API, GraphQL, and FTP connections, any of the following changes to a host or Base URI mid-month will result in a second endpoint being counted for the month:
-
Changing the domain (for example,
a.com→b.com) -
Switching between a domain name and an IP address, or vice versa
-
Changing the IP address to one in a different subnet (for example,
192.168.1.x→192.168.2.x)
Note
integrator.io counts a second endpoint only if you run a flow after making the change. Updating a connection's host or Base URI without running a flow doesn't add to your endpoint count. Switching back to a host or Base URI already counted earlier in the month also doesn't add a new count.
The universal connector count is also added to your endpoint app summary when any of them is referenced in a flow that is run.
Important
The URL comparison is case-insensitive, but it is otherwise very precise. The base URIs https://my-app-host.com/api/ and https://my-app-host.com/api/v3 for a token-based universal HTTP connection are not identical and will be counted separately. In most cases, you can simplify the base URI, adding Relative URI portions of the full path in the connection or flow steps, thereby reducing the endpoint app total.
-
Select the avatar in the upper right corner of the Home page to open account settings.
-
Select Subscription to view your entitlement usage.
-
Select View next to any entitlement for usage details.
Note
Audit your account entitlements and consider your usage before you make any changes to your subscription. For example, if you currently are entitled to five endpoints and you reduce your subscription limit to three endpoints, then two of those endpoints will be disabled. When the new subscription takes effect, flows to or from those missing endpoint won't be able to run.