Census changelog www.getcensus.com

Improvement

You can now make custom HTTP requests using your existing NetSuite credentials.

What's New

When you have a NetSuite destination connected, you'll see HTTP Request as an available object when creating a sync.

Why It Matters

• Fill integration gaps - Quickly sync to NetSuite REST API endpoints we don't support out-of-the-box, using credentials you've already configured
• Less setup friction - No need to set up a separate HTTP Request destination
• Leverage existing auth - Your NetSuite token-based authentication works automatically

How It Works

1. Select HTTP Request as the object when creating a sync
2. Enter your target NetSuite REST API endpoint (must be under https://.suitetalk.api.netsuite.com/services/rest/record/v1)
3. Configure the sync as you would for a standard HTTP Request destination

The sync will use your existing NetSuite connection's credentials automatically.

Read the docs →

Improvement

You can now configure Warehouse Writeback when creating or updating supported data sources through the Census API.

Set the warehouse_writeback_retention_in_days parameter to enable detailed sync logging to your warehouse and control how long logs are retained. Read more about Warehouse Writeback in the Census docs.

View API Reference →

New

We've expanded the Census API to make it easier to programmatically discover and inspect your data sources.

Tables

The new /sources/{id}/tables endpoint lets you retrieve all tables and views available in a source. This endpoint includes powerful filtering and sorting capabilities:

• Search: Filter tables using case-insensitive substring matching across table names, schemas, and catalogs

• Sort: Order results by table name, schema, or catalog in ascending or descending order

• Pagination: Navigate large result sets with configurable page sizes up to 100 results

View API Reference →

Tables can be refreshed from the source using the table refresh endpoint.

Columns

The /sources/{id}/tables/columns endpoint provides detailed column information for any table in your source, including data types and metadata.

View API Reference →

Columns can be refreshed for a table using the column refresh endpoint.

Getting Started

Both endpoints require a Bearer token from your workspace settings. Check out the API documentation for authentication details and complete parameter references.

Improvement

Our Jira connector now supports the Update sync behavior.

Improvement

Our Pylon connector now supports primary_domain as an identifier.

Improvement

Our Pinterest connector now supports conversions!

Improvement

We now support the Asset object for our Planhat connector.

New

We're excited to announce the Census Terraform Provider is now available on the Terraform Registry, enabling you to manage your Census resources as code!

What you can do:

• Define and version control your Census configurations in code
• Collaborate on changes through pull request reviews and approvals
• Automate deployment of resources across environments

Installation:

terraform {
  required_providers {
    census = {
      source  = "sutrolabs/census"
      version = "~> 0.2.0"
    }
  }
}

Links:

👉 Terraform Registry

👉 GitHub Repository

New

Generate AI-ready vector embeddings directly in Census and sync them to modern vector databases.

What's New

Embedding Columns - A new column type that generates vector embeddings from your text data using OpenAI's embedding models. Create embeddings as easily as adding a calculated column.

Vector Store Connections - Native support for Pinecone and turbopuffer. Sync enriched datasets with embeddings directly to vector databases, with automatic updates as your source data changes.

Why It Matters

Turn warehouse data into AI-ready vectors without custom pipelines. Build semantic search, similarity matching, and retrieval-augmented applications using the data you already have - with the same governance and lineage you rely on.

Use Cases

Semantic support search - Find similar tickets regardless of phrasing

CRM intelligence - Match accounts or leads based on unstructured notes

Knowledge base search - Let employees query documentation by meaning

Feedback analysis - Cluster customer comments by topic

👉Embedding Columns documentation

👉Pinecone destination documentation

👉turbopuffer destination documentation

Improvement

You can now make custom HTTP requests using your existing destination credentials, starting with HubSpot.

What's New
When you have a destination already connected, you'll see "HTTP Request" as an available object.

Why This Matters

• Fill integration gaps - Quickly sync to endpoints we don't support out-of-the-box, using credentials you've already configured. This expands the supported surface of all our destinations, including our most complex destinations where HTTP Requests were previously unable to be configured
• Customized behaviours - Take other actions like Merge or Convert Leads
• Less setup friction - No need to set up a separate destination

How It Works
Select HTTP Request as the object when creating a sync and configure the endpoint as outlined in our docs. The sync will use your existing connection's credentials automatically.

Need this now?
The HTTP Request object is currently available for the HubSpot destination, with more on the way. Reach out to support@getcensus.com if you'd like us to prioritize yours.