ScowttHelp Center

For Developers · Updated Nov 6, 2026

Let Scowtt pull from your API

If none of the other options fit, for example when your data is only available through a proprietary internal API, Scowtt can build a custom connector that pulls from your system every hour. It's the most resource-intensive option for both teams and is usually recommended only when no export to BigQuery, a storage bucket or SFTP is possible.

How it works: You share your API details and read-only credentials. Scowtt builds and tests a connector, runs the backfill, then pulls hourly.

Before you start

  • The person or team who owns the API and can answer detailed questions about it.
  • Read-only API credentials: OAuth client credentials, an API key and secret, or a service account token.

Steps

  1. You: Tell Scowtt which endpoints hold the data

    Scowtt needs leads or contacts, activities such as calls, texts, emails and appointments, quotes or opportunities, and purchases or revenue.

  2. You: Explain how to fetch only what changed

    For example, by filtering on an updated-at field since the last pull, and how pagination works.

  3. You: Create read-only credentials for Scowtt

    Tell your Scowtt team when they expire and how they rotate.

  4. You: Start any IP allowlist approval early

    If your API only accepts known IP addresses, ask your Scowtt team for Scowtt's outbound IP addresses on your first call. This approval often takes the longest.

  5. You: Send the technical package

    Through a secure channel: the base URL, with production and sandbox clearly labeled; the authentication method and credentials; endpoint documentation such as a Swagger file or Postman collection; example responses; and any rate limits or usage restrictions.

  6. Scowtt: Build and test the connector

    Scowtt scopes the work, shares a timeline, then tests authentication, pagination, consistent results across pulls, and the key ID, timestamp and outcome fields.

  7. Scowtt: Run the backfill and turn on hourly pulls

    Scowtt runs the historical backfill, validates it with you, then switches to hourly pulls.

Good to know

  • Tell your Scowtt team before changing the API, its fields or its credentials, so pulls don't fail silently.
  • Make sure Scowtt's pulls fit within your rate limits alongside your other traffic.
  • To end access, revoke the credentials.

Who does what

StepWhoWhat changes hands
Tell Scowtt which endpoints hold the dataYouList of endpoints
Explain how to fetch only what changedYouHow to filter and paginate
Create read-only credentials for ScowttYou—
Start any IP allowlist approval earlyYouScowtt's outbound IP addresses (from Scowtt)
Send the technical packageYouBase URL, auth method and credentials, docs, examples, rate limits
Build and test the connectorScowttA timeline
Run the backfill and turn on hourly pullsScowttConfirmation that data is flowing
Push data to Scowtt's APIIf your team has development resources and wants to send data directly, Scowtt can provide an API endpoint for your systems to push to. Because the API is flexible across customers, it starts with a short mapping exercise to align your fields with what Scowtt expects.Choose how to connect your dataThere are several ways to share CRM and analytics data with Scowtt. Your Scowtt team will help you pick the one that fits your environment best.