megachangelog
Announcement

API V2 Beta Endpoints Now Available

Census introduces the first V2 API endpoints with a new Sources API that supports region and storage backend selection, Group ID management for access controls, and Personal Access Token authentication. Workspaces have been removed from the API and Workspace API Keys are no longer supported.

 

Coming Soon

  

We've very excited to show you the first of our V2 API endpoints: Sources. This new endpoint captures some of the changes we'll be making in the coming weeks mentioned in our Migration FAQ.

In particular, this new Sources API captures a few important changes:

  • Specify a region and storage backend when creating an activation source
  • Get a Group ID - All warehouse connections in Fivetran have a Group ID and activation sources are no different.
    • You'll use Group IDs to manage access controls to the activation source and its associated activations via the Fivetran API, which means you'll now need a Fivetran API key as well.
  • Workspaces do not appear at all in the URL and Workspace API Keys are no longer supported. Only Personal Access Tokens (PATs) can be used with API V2.

This API isn't ready for production use yet but we want to open it up now so you get a sense of the changes coming very soon. Stay tuned for more!

apibetasourcesauthenticationmigration

Source: original entry ↗

More from Census

Follow Census to get its new changes in your feed and email digest.

Improvement

Braze: Email and User Alias as Identifiers

The Braze connector now supports email and user_alias as user identifiers for Event and PurchaseEvent syncs, alongside the existing external_id option, providing more flexibility in data synchronization.

brazeconnectorsidentifiersevents
Improvement

LinkedIn Conversions: lead as an Optional Field

LinkedIn Conversions now supports an optional lead field to map Lead Gen Form Response IDs and attribute conversion events to specific lead forms.

linkedinconversionsintegrationslead-forms
Improvement

SFTP: Atomic File Uploads

SFTP destination now supports atomic uploads by writing to a temporary path first and publishing to the final path only after completion, preventing downstream processes from reading partial files. This feature can be enabled in Advanced Configuration with an optional custom temp file directory.

sftpuploadsdata-integrityreliability
See all Census changes →