- Getting Started
- Demo Videos
- Blueprint
- Rivers
- Rivers List & Groups
- Source to Target River
- Logic River
- Action River
- Settings Tab
- Sources
- Applications
- Reconnecting to an Existing OAuth2 Connection in Rivery
- Active Campaigns
- Adaptv
- Adaptive Planning
- Adjust
- Adobe Ads
- Adobe Analytics
- Adroll
- Adtelligent (Verta Media)
- Airtable
- Amplitude
- Anaplan
- Apple Search Ads
- AppNexus
- Appsflyer
- Appstore Connect - Sales and Trends
- Appstore Connect - Apps Analytics
- Avantlink
- AWS Billing
- Bing Ads
- BlueSnap
- Branch
- Brandwatch
- Bronto
- CallRail
- Cellxpert
- Content.Ad
- Coupa
- CreativeX (Picasso Labs)
- Crimson Hexagon
- Criteo
- Criteo V2023 -10
- Customer Gauge
- Currency Service
- Dear Systems
- Delta Projects
- Digital Turbine
- Display & Video 360
- Docebo
- DoubleClick DCM
- Ex-Co
- Facebook Ads
- Facebook Audience Network
- Facebook Social
- Freshservice
- Genesys
- GMP365
- Google Ad Manager (DoubleClick for Publishers)
- Google Ads
- Google Analytics
- Google Play Store
- Google Search Console
- GothamAds
- Greenhouse
- Harvest
- Hibob
- HiveStack
- HubSpot
- Impact Radius
- Index Exchange
- Innovid
- Iron Source
- Instagram Social
- Intercom
- Jira
- JWPlayer
- JWPlayer Analytics
- Kantata (Mavenlink)
- Keepcon
- Klaviyo
- Kochava
- LinkedIn Ads
- Linkedin Social
- LKQD
- Magento
- Marketo
- Maxio Chargify
- Mediamath
- MixPanel
- Moat Analytics
- MobileAction
- Monday
- MyAffiliates
- NetSuite APIs
- Nium
- Nuviad
- Optimove
- Outbrain
- PayPal Reports
- Pendo
- Pepperjam
- Quickbooks
- Recharge
- Recurly
- Reddit Ads
- Revcontent
- Sage Intacct
- Sailthru
- Salesforce
- Salesforce Audience
- Salesforce Marketing Cloud
- Salesforce Pardot
- SAP Concur
- Search Ads 360 Reporting
- Sendgrid
- Sensor Tower
- Servicenow
- ShareASale
- ShipHero
- Shopify
- Skai
- Snapchat Marketing
- Socialbakers
- Social Studio
- Spotx
- Sprinklr
- StackAdapt
- Streamrail
- Stripe
- SuccessFactors
- SurveyGizmo
- SurveyMonkey
- Taboola
- The Trade Desk
- Tiger Pistol
- Tiktok
- TrendKite
- Tune (HasOffers)
- UXCam
- Verizon Media (Oath)
- X (Twitter)
- Yahoo Ads
- Yandex
- Yotpo
- YouTube
- Zendesk
- Zendesk Chat
- Zendesk Talk
- Databases
- Databases Overview
- Database Connectivity Options
- Database River Modes
- Automatic Schema Drift Management
- Database Table Configuration Options
- CDC 'Point in Time' Position
- BigQuery
- Datastore
- ElasticSearch
- MariaDB
- Microsoft SQL Server
- MongoDB
- MySQL
- Oracle
- PostgreSQL
- Snowflake as a Source
- Teradata
- Vertica
- Events
- Storage & Files
- Rest API
- Applications
- Targets
- Administration
- Security
- REST API
- Support
- Troubleshooting
- Error Messages
- Azure SQL
- Google BigQuery as a Source
- CellExpert
- Conversion Service
- Coupa
- Criteo V2024-07
- DataFrame
- Deployment
- Docebo
- DoubleClick Publisher
- Display & Video 360
- RVR-DC-001
- RVR-DC-100
- RVR-DC-216
- RVR-DC-207
- RVR-DV-219
- RVR-DV-218
- RVR-DC-210
- RVR-DV-303
- RVR-DV-003
- RVR-DV-223
- RVR-DV-209
- RVR-DV-217
- RVR-DV-222
- RVR-DV-206
- RVR-DV-201
- RVR-DC-300
- RVR-DC-211
- RVR-DC-202
- RVR-DV-304
- RVR-DV-210
- RVR-DC-205
- RVR-DV-205
- RVR-DV-211
- RVR-DV-207
- RVR-DV-212
- RVR-DV-102
- RVR-DV-204
- RVR-DV-208
- RVR-DV-202
- RVR-DV-213
- RVR-DV-100
- RVR-DV-221
- RVR-DV-301
- RVR-DV-302
- RVR-DV-300
- RVR-DV-220
- RVR-DV-216
- RVR-DV-215
- RVR-DV-002
- RVR-DV-224
- RVR-DV-225
- RVR-DV-214
- RVR-DV-200
- RVR-DV-203
- RVR-DV-001
- RVR-DC-302
- RVR-DV-101
- RVR-DC-209
- RVR-DC-216
- RVR-DC-203
- RVR-DC-208
- RVR-DC-301
- RVR-DC-206
- RVR-DC-214
- RVR-DC-200
- RVR-DC-101
- RVR-DC-215
- RVR-DC-201
- RVR-DC-212
- RVR-DC-213
- RVR-DC-204
- Elasticsearch
- Mixpanel
- Microsoft SQL Server
- NetSuite
- NetSuite Analytics
- NetSuite RESTlets
- Pepperjam
- Pipedrive
- PostgreSQL
- Python
- QuickBooks
- RDBMS
- RVR-SF-RDBMS-315
- RVR-SF-RDBMS-317
- RVR-SF-RDBMS-316
- RVR-SF-RDBMS-305
- RVR-SF-RDBMS-307
- RVR-RDBMS-403
- RVR-RDBMS-401
- RVR-RDBMS-305
- RVR-RDBMS-202
- RVR-SF-RDBMS-318
- RVR-SF-RDBMS-314
- RVR-SF-RDBMS-313
- RVR-SF-RDBMS-312
- RVR-SF-RDBMS-311
- RVR-SF-RDBMS-308
- RVR-SF-RDBMS-310
- RVR-SF-RDBMS-309
- RVR-SF-RDBMS-302
- RVR-SF-RDBMS-304
- RVR-SF-RDBMS-306
- RVR-SF-RDBMS-303
- RVR-SF-RDBMS-301
- RVR-RDBMS-312
- RVR-RDBMS-313
- RVR-RDBMS-314
- RVR-RDBMS-311
- RVR-RDBMS-309
- RVR-RDBMS-310
- RVR-RDBMS-402
- RVR-RDBMS-304
- RVR-RDBMS-308
- RVR-RDBMS-201
- RVR-RDBMS-101
- RVR-RDBMS-307
- RVR-RDBMS-306
- RVR-RDBMS-301
- RVR-RDBMS-303
- RDBMS API
- Recurly
- Amazon Redshift
- REST Action
- Rivery Configuration Error
- Amazon S3
- SAP Concur
- Salesforce Marketing Cloud
- Snowflake
- StackAdapt
- Storages
- SuccessFactors
- Release Notes
- 2025
- 2024
- December 2024 Release Notes
- November 2024 Release Notes
- October 2024 Release Notes
- September 2024 Release Notes
- August 2024 Release Notes
- July 2024 Release Notes
- June 2024 Release Notes
- May 2024 Release Notes
- April 2024 Release Notes
- March 2024 Release Notes
- February 2024 Release Notes
- January 2024 Release Notes
- 2023
- December 2023 Release Notes
- November 2023 Release Notes
- October 2023 Release Notes
- September 2023 Release Notes
- August 2023 Release Notes
- July 2023 Release Notes
- June 2023 Release Notes
- May 2023 Release Notes
- April 2023 Release Notes
- March 2023 Release Notes
- February 2023 Release Notes
- January 2023 Release Notes
- 2022
- December 2022 Release Notes
- November 2022 Release Notes
- October 2022 Release Notes
- September 2022 Release Notes
- August 2022 Release Notes
- July 2022 Release Notes
- June 2022 Release Notes
- May 2022 Release Notes
- April 2022 Release Notes
- March 2022 Release Notes
- February 2022 Release Notes
- January 2022 Release Notes
- 2021
- API Upgrades Changelog
- API Upgrade Overview
- 2025
- 2024
- 2024-12 Campaign Manager 360 Fields Update
- 2024-10 Shopify API Upgrade v2024-10
- 2024-10 Monday API Upgrade v2024-10
- 2024-08 Display & Video 360 Upgrade v3
- 2024-08 Google Ads Upgrade v17
- 2024-08 LinkedIn Social Upgrade v202406
- 2024-08 LinkedIn Ads Upgrade v202406
- 2024-08 Google Ad Manager Upgrade v202405
- 2024-07 Pendo Upgrade
- 2024-05 Adjust API Upgrade
- 2024-05 Search Ads 360 API Upgrade
- 2024-05 Klaviyo Legacy v1 and v2 to v2024-02-15 API Migration
- 2024-03 Facebook Social Deprecated Metrics
- 2024-02 Shopify API Upgrade v2024-01
- 2024-02 Google Ads API Upgrade V15
- 2024-02 Airtable API Keys Deprecation
- 2024-01 Instagram Social Upgrade to Graph API v18
- 2024-01 Criteo API Upgrade v2023-10
- 2024-01 Google Ad Manager upgrade to v202311
- 2024-01 Monday API Upgrade v2024-01
- 2024-01 Facebook Ads - Marketing API Upgrade v18
- 2023
Is there a limit on how much data can be sent in a single request?
Yes, there is a limit of 8 MB per request.
However, it is recommended to divide data into smaller-sized payloads and send them in a higher number of requests.
This approach ensures better performance and reduces the likelihood of encountering issues with data transmission or processing.
Are there any constraints on the number of events that can be received via a Webhook?
Rivery handles up to 10,000 events within a 5-minute duration per IP address.
Exceeding this limit may result in dropped events, so it is important to implement appropriate rate-limiting mechanisms on the sender side.
What is the retention time for data posted to the Webhook endpoint?
The data posted to the Webhook endpoint is retained for 72 hours.
After this period, the data will no longer be available for processing.
If the customer posts multiple times to the endpoint before the Source to Target River is scheduled to run, will all data be retained and loaded?
Yes, all data posted to the Webhook endpoint will be retained.
Rivery does not overwrite previously posted data with subsequent posts. When the Source to Target River runs, it will process all retained data up to that point.
What happens if a post request to the Webhook endpoint fails? Is a notification sent to the user?
In the event of a failure, the Webhook endpoint will return an appropriate HTTP response code:
- 500-series codes indicate server-side issues.
- 400-series codes indicate client-side issues.
Rivery does not automatically send notifications to the user. It is the responsibility of the sender's system to monitor these responses and implement a notification mechanism for failed attempts. This ensures that the sender is promptly informed about any delivery issues and can take corrective action.
For additional details or specific use-case questions, please contact our support team.
Table of contents
- Is there a limit on how much data can be sent in a single request?
- Are there any constraints on the number of events that can be received via a Webhook?
- What is the retention time for data posted to the Webhook endpoint?
- If the customer posts multiple times to the endpoint before the Source to Target River is scheduled to run, will all data be retained and loaded?
- What happens if a post request to the Webhook endpoint fails? Is a notification sent to the user?