LogoLogo
  • 🦩Overview
  • 💾Datasets
    • Overview
    • Core Concepts
      • Columns & Annotations
      • Type & Property Mappings
      • Relationships
    • Basic Datasets
      • dbt Integration
      • Sigma Integration
      • Looker Integration
    • SaaS Datasets
    • CSV Datasets
    • Streaming Datasets
    • Entity Resolution
    • AI Columns
      • AI Prompts Recipe Book
    • Enrichment Columns
      • Quick Start
      • HTTP Request Enrichments
    • Computed Columns
    • Version Control
  • 📫Syncs
    • Overview
    • Triggering & Scheduling
    • Retry Handling
    • Live Syncs
    • Audience Syncs
    • Observability
      • Current Sync Run Overview
      • Sync History
      • Sync Tracking
      • API Inspector
      • Sync Alerts
      • Observability Lake
      • Datadog Integration
      • Warehouse Writeback
      • Sync Lifecycle Webhooks
      • Sync Dry Runs
    • Structuring Data
      • Liquid Templates
      • Event Syncs
      • Arrays and Nested Objects
  • 👥Audience Hub
    • Overview
    • Creating Segments
      • Segment Priorities
      • Warehouse-Managed Audiences
    • Experiments and Analysis
      • Audience Match Rates
    • Activating Segments
    • Calculated Columns
    • Data Preparation
      • Profile Explorer
      • Exclusion Lists
  • 🧮Data Sources
    • Overview
    • Available Sources
      • Amazon Athena
      • Amazon Redshift
      • Amazon S3
      • Azure Synapse
      • ClickHouse
      • Confluent Cloud
      • Databricks
      • Elasticsearch
      • Kafka
      • Google AlloyDB
      • Google BigQuery
      • Google Cloud SQL for PostgreSQL
      • Google Pub/Sub
      • Google Sheets
      • Greenplum
      • HTTP Request
      • HubSpot
      • Materialize
      • Microsoft Fabric
      • MotherDuck
      • MySQL
      • PostgreSQL
      • Rockset
      • Salesforce
      • SingleStore
      • Snowflake
      • SQL Server
      • Trino
  • 🛫Destinations
    • Overview
    • Available Destinations
      • Accredible
      • ActiveCampaign
      • Adobe Target
      • Aha
      • Airship
      • Airtable
      • Algolia
      • Amazon Ads DSP (AMC)
      • Amazon DynamoDB
      • Amazon EventBridge
      • Amazon Pinpoint
      • Amazon Redshift
      • Amazon S3
      • Amplitude
      • Anaplan
      • Antavo
      • Appcues
      • Apollo
      • Asana
      • AskNicely
      • Attentive
      • Attio
      • Autopilot Journeys
      • Azure Blob Storage
      • Box
      • Bloomreach
      • Blackhawk
      • Braze
      • Brevo (formerly Sendinblue)
      • Campaign Monitor
      • Canny
      • Channable
      • Chargebee
      • Chargify
      • ChartMogul
      • ChatGPT Retrieval Plugin
      • Chattermill
      • ChurnZero
      • CJ Affiliate
      • CleverTap
      • ClickUp
      • Constant Contact
      • Courier
      • Criteo
      • Crowd.dev
      • Customer.io
      • Databricks
      • Delighted
      • Discord
      • Drift
      • Drip
      • Eagle Eye
      • Emarsys
      • Enterpret
      • Elasticsearch
      • Facebook Ads
      • Facebook Product Catalog
      • Freshdesk
      • Freshsales
      • Front
      • FullStory
      • Gainsight
      • GitHub
      • GitLab
      • Gladly
      • Google Ads
        • Customer Match Lists (Audiences)
        • Offline Conversions
      • Google AlloyDB
      • Google Analytics 4
      • Google BigQuery
      • Google Campaign Manager 360
      • Google Cloud Storage
      • Google Datastore
      • Google Display & Video 360
      • Google Drive
      • Google Search Ads 360
      • Google Sheets
      • Heap.io
      • Help Scout
      • HTTP Request
      • HubSpot
      • Impact
      • Insider
      • Insightly
      • Intercom
      • Iterable
      • Jira
      • Kafka
      • Kevel
      • Klaviyo
      • Kustomer
      • Labelbox
      • LaunchDarkly
      • LinkedIn
      • LiveIntent
      • Loops
      • Mailchimp
      • Mailchimp Transactional (Mandrill)
      • Mailgun
      • Marketo
      • Meilisearch
      • Microsoft Advertising
      • Microsoft Dynamics
      • Microsoft SQL Server
      • Microsoft Teams
      • Mixpanel
      • MoEngage
      • Mongo DB
      • mParticle
      • MySQL
      • NetSuite
      • Notion
      • OneSignal
      • Optimizely
      • Oracle Database
      • Oracle Eloqua
      • Oracle Fusion
      • Oracle Responsys
      • Orbit
      • Ortto
      • Outreach
      • Pardot
      • Partnerstack
      • Pendo
      • Pinterest
      • Pipedrive
      • Planhat
      • PostgreSQL
      • PostHog
      • Postscript
      • Productboard
      • Qualtrics
      • Radar
      • Reddit Ads
      • Rokt
      • RollWorks
      • Sailthru
      • Salesforce
      • Salesforce Commerce Cloud
      • Salesforce Marketing Cloud
      • Salesloft
      • Segment
      • SendGrid
      • Sense
      • SFTP
      • Shopify
      • Singular
      • Slack
      • Snapchat
      • Snowflake
      • Split
      • Sprig
      • Statsig
      • Stripe
      • The Trade Desk
      • TikTok
      • Totango
      • Userflow
      • Userpilot
      • Vero Cloud
      • Vitally
      • Webhooks
      • Webflow
      • X Ads (formerly Twitter Ads)
      • Yahoo Ads (DSP)
      • Zendesk
      • Zoho CRM
      • Zuora
    • Custom & Partner Destinations
  • 📎Misc
    • Credits
    • Census Embedded
    • Data Storage
      • Census Store
        • Query Census Store from Snowflake
        • Query Census Store locally using DuckDB
      • General Object Storage
      • Bring Your Own Bucket
        • Bring your own S3 Bucket
        • Bring your own GCS Bucket
        • Bring your own Azure Bucket
    • Developers
      • GitLink
      • Dataset API
      • Custom Destination API
      • Management API
    • Security & Privacy
      • Login & SSO Settings
      • Workspaces
      • Role-based Access Controls
      • Network Access Controls
      • SIEM Log Forwarding
      • Secure Storage of Customer Credentials
      • Digital Markets Act (DMA) Consent for Ad Platforms
    • Health and Usage Reporting
      • Workspace Homepage
      • Product Usage Dashboard
      • Observability Toolkit
      • Alerts
    • FAQs
Powered by GitBook
On this page
  • Create a destination
  • Create a sync
  • Select your source
  • Select your destination
  • Choose your request trigger
  • Specify the number of records per request
  • Select a sync key
  • Choose a request method
  • Choose your payload type
  • Define your payload
  • Configure rate limits
  • Save and run your sync
  • Error Handling
  • FAQs
  • Need help using HTTP Request?

Was this helpful?

  1. Destinations
  2. Available Destinations

HTTP Request

Send data anywhere that accepts standard HTTP requests.

PreviousHelp ScoutNextHubSpot

Last updated 3 months ago

Was this helpful?

Overview

Our HTTP Request destination is a Swiss Army knife. It allows you to send data to any service that accepts standard HTTP requests—including standard SaaS APIs and internal systems—and only takes a few minutes to set up via our no-code interface.

To demonstrate how it works, let's look at a real-world example of when new rows appear in your source data. If you want to follow along, you can create a new Brevo account .

Create a destination

  • Navigate to the Destinations page in Census.

  • Click New Destination and select HTTP Request from the menu.

  • Name your destination and enter the Base URL for the Brevo API (https://api.brevo.com).

  • and copy it to your clipboard.

  • Click Add Header, name the header api-key (per Brevo's docs), paste your API key under Value, and check the box indicating it's a secret (this will hide it in our UI if you or anyone else attempts to edit this connection later on).

  • Click Connect to continue.

Create a sync

Navigate to the Syncs page in Census and click New Sync.

Select your source

In this example, we'll use data from a demo Redshift cluster but this could be any source that we support.

Select your destination

Select the HTTP Request destination you just created and input the specific endpoint we'll be using to create contacts in Brevo.

Choose your request trigger

Choose the trigger that you want Census to monitor in your source data.

Specify the number of records per request

Census allows you to either send one record at a time or batch records for better performance when the destination allows for it. In this case, we'll keep things simple and send one record at a time (which is also what this particular endpoint expects).

[
  {% for record in records %}
  {
    "id": "{{ record['ID'] }}",
    "name": "{{ record['NAME'] }}"
  },
  {% endfor %}
]

The records will be set to an array containing all of the records to be sent in the current request.

Select a sync key

This helps Census identify unique records in your source data.

Choose a request method

Census supports all major HTTP request methods. In this case, the endpoint we're syncing to expects a POST request.

Choose your payload type

We currently support the two most common payload types—empty and JSON. If you need more (e.g. XML, SOAP), please send us an email at support@getcensus.com!

This endpoint expects JSON, so we'll go with that.

Define your payload

Census provides three different ways of defining a payload.

  • Single source column: select a single column from your source data that contains the entire JSON payload you want to send.

  • Multiple source columns: select multiple columns from your source data. Census will combine them into a JSON payload with each column represented as a top-level key-value pair.

We'll use the template editor for this example so we can construct a payload that exactly matches what the Brevo API expects.

Configure rate limits

Brevo's contact endpoints have a rate limit of 10 requests per second (RPS). We can specify that here so that Census respects that limit when sending data.

Once you've saved and run your sync, head over to the API Inspector tab in your sync configuration to confirm the data was sent as expected. In this case, it was and we can confirm the record made it to our contact list in Brevo!

Error Handling

Census will use the HTTP response status code to determine whether records were accepted by the target service. Here is how various response status codes are interpreted:

  • 2xx - Success. All records sent in the request were accepted by the destination.

  • 4xx - Client failure in the batch. All records sent in the request were rejected by the destination. The sync will continue, but the records sent in the batch will be marked as rejected and reattempted next time the sync is run.

    • NOTE: a 429 status code will trigger up to 7 request retries with exponential backoff

  • 5xx - Server failure. The request will be retried up to 7 times with exponential backoff. If the request is unsuccessful within 7 retries, the entire sync will be failed.

FAQs

How do I configure a HTTP Destination to use basic auth?

Some destinations may use basic authorization instead of an API key.

This can be done by base64 encoding the username and password with the following format:

<username>:<password>

Then adding that as a header to the HTTP Request destination which should look like this: Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=

Need help using HTTP Request?

Note: in this example, the endpoint is static (i.e. /v3/contacts), but we also support using the language to populate values dynamically. For example, if we were sending requests to update existing contacts, we might need to include contact IDs in the endpoint like this: /v3/contacts/{{ record["id"] }}.

If you are using multiple records per request together with a JSON template payload, you will commonly need to use a Liquid for like this using the special records:

Template editor: using the Liquid template language to define an entirely custom payload. This is the most flexible option but requires a bit of elbow grease. See our full documentation to for more information.

Save and run your sync

via support@getcensus.com or start a conversation via the chat.

🛫
👏
Liquid
template
Liquid templates
Contact us
in-app
creating contacts in Brevo
here
Generate a new API key in Brevo
loop
Create your HTTP Request destination.