Articles in this section

Track your endpoint usage

Anitha Abraham
Updated

An endpoint is an application, database, or universal service that your flows and APIs reach through a connection. Your integrator.io subscription allows a set number of distinct endpoints per environment, and several connections to the same place usually count as one. This article explains what triggers an endpoint count, how connections consolidate into endpoints in each category, what never counts, and what to check before you reduce your subscription. To see your current count, go to Account avatar-icon.png, select Subscription, and then select View next to Endpoints invoked.

What counts as an endpoint

Endpoints are counted by what ran, not by which connections exist. A connection adds to your count the first time in a month that something runs through it:

  • A flow run counts every connection its steps reach: export and import steps, a Tool step's connections, and an AI agent step's Celigo Tools and MCP connections (MCP connections are grouped by server URL).
  • An API Builder call counts the same way, including Tool steps inside the API, and when the API is exposed as an entry on an MCP server.
  • A standalone export or import invoke counts its connection.

These don't count as endpoints:

  • A Tool called directly through its invoke URL or through an MCP server. These calls are metered as MCP calls, AI actions, or API calls instead (see Track your AI agent actions, credits, and MCP call usage and Track your API usage).
  • An upstream MCP server proxied through a Celigo MCP server. The proxy's MCP connection isn't counted; the calls are MCP calls.
  • An export or import invoked through a JavaScript API.
  • Connections to the Celigo integrator.io API, so cloning templates and reading flow errors through the API never use an endpoint.
  • Webhooks, which push data in rather than acting as a destination.
  • Anything run by a data loader flow.

How connections consolidate into endpoints

Your endpoint total is the sum of three categories. Within each, connections to the same place count as one endpoint. The rules apply in production and sandbox alike.

App connectors

Prebuilt connectors such as Acumatica, Salesforce, or Shopify. All connections that use the same connector count as one endpoint, whatever their store, account ID, or authentication type. Different connectors to the same backend are different endpoints; for example, NetSuite and NetSuite JDBC are two.

Examples: app connectors

  • Two NetSuite connections with different account IDs: 1 endpoint.
  • One NetSuite connection and one NetSuite JDBC connection: 2 endpoints.
  • One basic-auth and one OAuth 2.0 connection to Acumatica: 1 endpoint.
  • Three Shopify connections for three stores: 1 endpoint.

Databases

Database connections count as one endpoint when they share a host:

Examples: databases

  • Two MySQL connections to mysql.yoursql.io: 1 endpoint. Two to mysql1.yoursql.io and one to mysql2.yoursql.io: 2 endpoints.
  • Two Snowflake connections to the same <AccountName>.snowflakecomputing.com: 1 endpoint. Connections to two account names: 2 endpoints.
  • Two Amazon Redshift connections in the same cluster and region plus one in another: 2 endpoints.
  • Two DynamoDB connections with the same access key ID: 1 endpoint. With different access key IDs: 2 endpoints.

Universal connectors

HTTP, REST API, GraphQL, FTP, AS2, and wrappers. integrator.io compares the address text to decide whether connections point to the same endpoint:

  • HTTP, REST API, and GraphQL – Connections with an identical base URI count as one, whatever their authentication type. The comparison ignores case but is otherwise exact: https://my-app-host.com/api/ and https://my-app-host.com/api/v3 are two endpoints, and so are ftp://ftp.my-app-host.net and ftp://ftp.my-app-host.net/.
  • FTP (including SFTP and FTPS) and AS2 – Connections to the same server (domain name or IP address) and port count as one.
  • Wrappers – Each wrapper used in a flow run is its own endpoint.
  • A universal connection and a prebuilt connector to the same service are counted separately.

Tip: To use fewer endpoints, keep the connection's base URI broad and put the rest of the path in the relative URI of each flow step.

Examples: universal connectors

  • One basic-auth and three OAuth 2.0 HTTP connections to https://my-app-host.com: 1 endpoint.
  • Two HTTP connections to https://my-app-host.com/api/ and one to https://api.my-app-host.com/: 2 endpoints.
  • One HTTP connection to https://api.fieldaware.net and one prebuilt FieldAware connection: 2 endpoints.
  • Two FTP connections to ftp://ftp.my-app-host.net: 1 endpoint. One each to ftp.my-first-app-host.net and ftp.my-second-app-host.net: 2 endpoints.

Changing a host during the month

Changing a database host or a universal connection's base URI or server mid-month counts a second endpoint for that month only if a flow runs after the change. Changing the domain, switching between a domain name and an IP address, or moving to an IP address in a different subnet all count as a new host. Switching back to a host already counted that month doesn't add another.

Before you reduce your subscription

Caution: Check your endpoint usage before lowering your limit. If you're using five endpoints and reduce your subscription to three, two endpoints are disabled when the new subscription takes effect, and flows to or from them can't run. Have the credentials for your connections ready whenever you edit them to consolidate endpoints.