Census
Census, now operating as Fivetran Activations following its acquisition by Fivetran, is a reverse ETL and data activation platform that turns the data warehouse into the operational source of truth for go-to-market and product teams. The platform configures managed, no-code reverse ETL pipelines that move modeled data from warehouses like Snowflake, BigQuery, Databricks, and Redshift into more than 200 SaaS destinations across CRM, marketing automation, advertising, customer success, product, finance, and productivity tools. Census also offers an Audience Hub for visual segment building, an Embedded product for white-labeling reverse ETL inside customer-facing applications, and a Connect workflow for collecting end-user credentials and programmatically creating sync pipelines. Developers integrate through the Census Management API, Embedded API, Connect Links, custom destination APIs, and a Terraform provider. This profile covers the Census product line and is distinct from the US Census Bureau public APIs.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Census the way a machine reads it — 9 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Census scores 20.6/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Census
Each block below is one kind of artifact we hold for Census. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Census Management API
REST API for managing reverse ETL syncs, sources, destinations, datasets, models, and segments programmatically. Used to provision, update, and monitor Census workspaces, schedu...
Census Embedded API
REST API for embedding reverse ETL inside SaaS products, giving customers more than 200 prebuilt connectors out of the box. Combines Management API operations with Connect Links...
Census Connect
Client-side workflow that streamlines collection of end-user credentials and programmatically creates reverse ETL pipelines, in combination with the Census Management API.
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Census GraphQL Schema
This conceptual GraphQL schema represents the Census (Fivetran Activations) reverse ETL and data activation platform. Census enables engineering and data teams to synchronize mo...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Census Co Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Census Co Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Census — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/census-co · machine-readable index on apis.io