AccessLayer
Platform
Core Concepts

Connectors

How connectors model external systems and power data collection in AccessLayer.

Connectors define how AccessLayer fetches data from external systems such as Stripe, GitHub, and Notion. Technically, a connector describes the HTTP endpoints and request patterns AccessLayer can use to collect source data.

At a glance

  • An organization can have many connectors.
  • You can connect the same provider multiple times, such as multiple Stripe accounts.
  • AccessLayer collects data in parallel while respecting provider rate limits.
  • Query-time collection data is cached for 5 minutes.

Browse all connectors

For setup guides and required fields, see All connectors.

Using multiple connections of the same provider

You can connect multiple instances of the same connector, such as separate Stripe accounts.

Use clear names so each connection is easy to identify during setup and querying. For example:

  • Stripe - US
  • Stripe - EU
  • Stripe - Sandbox

Note: Good names reduce mistakes when you have similar accounts in one organization.

Rate limits

  • AccessLayer collects data in parallel as much as possible to reduce collection time.
  • Collection is rate-limit aware, so requests are coordinated to avoid hitting provider limits.

Note: Each provider has different rate-limit rules, so collection speed can vary by connector.

Cache window

AccessLayer caches collection data used during queries for 5 minutes. This helps reduce duplicate API calls and lowers connector load.

On this page