These features are only available for Census Embedded customers. If you don’t see these options, please reach out to Customer Support.

Connect Links allow your customers to seamlessly authenticate their services, making them available as sources & destinations in your Census workspace.

Collecting credentials is easy.

  1. Generate a connect link for your customer.
  2. Your customer enters their credentials.
  3. The connection appears in your Census workspace.

By default, Connect Links will expire after 24 hours. If you’d like them to last longer for your account, you can update this setting in your organization settings. You can also customize where users will be redirected after authorizing a new connection, as well as the logo that is used.

We will use destination connect links in this guide. Source connect links are also available.

You can create a Connect Link through both the Census UI and the API.

Generating Connect Links via the UI is not commonly used as a long term approach for true Census Embedded customers, but it can be useful when starting out to get a feel for what your end-users will experience.


Generate Connect Link URL

From the destinations page in the Census UI, select “Add a Destination”, search for the destination type your customer is hoping to connect, and select “Next”. Generate the Connect Link URL with the “Create link” button.


Navigate to the Connect Link URL

You can now copy the Connect Link URL and either send it to your customer via Slack or in an email. Or, if you’d like to embed the connection flow directly in your app, check out our embedded connect links guide.


Complete Authorization of Destination

Your customer (or you) should then go through the Connect Link authorization flow with the destination. The Connect Link UI will handle

  1. Gathering all the required credentials for the destination.
  2. Performing a series of automated tests against the destination.

Once complete, the new destination connection will be available for use on the destinations page or via the destination APIs.