Connector
Private or internal API → your warehouse
The case no connector platform can serve at any price, because the API is not on the public internet and never will be.
What it costs
Two kinds of line. The connector is the technical connection to this source, charged once. The data models are the datasets you actually asked for, priced by type.
- Build
- Base Connector · Complex source · incl. 3 data models
- Price
- See the price list
Data models customers ask for on this kind of source
Three Simple ones come with the Base Connector. These are what tends to get added.
| Data model | Typical type | API resources it usually needs |
|---|---|---|
| Pricing | Advanced | /prices, /price-rules, /currencies |
| Entitlements | Advanced | /accounts, /entitlements, /plans |
| Usage | Standard | /usage |
Illustrative, not a quote: the type is assessed per customer from the API's own documentation. Note the last column — those resources are included in the data model price, not charged separately, and their raw data lands in your warehouse too.
What decides the type
- Whether an IP allowlist is enough, or a VPN is required
- Your network team's availability — usually the critical path
- Whether the API was designed for external consumption at all
- Documentation quality, which for internal APIs is usually the README
What you get
- A connector running inside your own network perimeter
- Static egress IP or private connectivity, defined as code
- Incremental sync, checkpointing, backfill and monitoring as standard
- Documentation of the API's actual behaviour, which often did not exist before
- Source code, infrastructure and credentials in your accounts
Why this is the clearest case for a custom build
A hosted connector platform cannot reach an API that is not publicly addressable. That is not a gap in their product; it is what “hosted” means. The options are to expose your internal service to the internet, or to run the connector inside your own network.
We run it inside your network. It is your cloud project, your VPC, your egress IP.
The honest constraint
The engineering is often straightforward. The calendar is not. A site-to-site VPN or a private interconnect involves your network team, a change window and sometimes a third party. We exclude that time from the quoted delivery window and say so in the estimate, because pretending otherwise is how a fixed date gets missed for reasons nobody controlled.
A side effect worth mentioning
Internal APIs are rarely documented. By the end of the build there is a written description of how yours actually behaves — what it returns, what it does when you page past the end, which fields are unreliable. Several customers have found that more useful than the connector.
Get an estimate for private or internal api → your warehouse
Send the documentation link. You get a complexity tier, a recommended architecture, a fixed price and a delivery window — free, usually the same day. If a vendor connector would serve you better, we will say that instead.
Get an estimate