Ingest JSON events via HTTP.
Feature name | Supported | Notes |
---|---|---|
Event collection | ✅ | Collects events in JSON format. |
Real-time updates | ✅ | See the Real-time updates section. |
Real-time deletes | ✅ | See the Real-time deletes section. |
Batch Delete API | ✅ | See Batch Delete API. |
Batch Update API | ✅ | See Batch Update API. |
Bulk insert | ✅ | Up to 500 events per HTTP request. |
API configurable | ✅ | See API docs. |
Terraform configurable | ✅ | See Terraform docs. |
Column | Type | Description |
---|---|---|
_propel_received_at | TIMESTAMP | The timestamp when the event was collected in UTC. |
_propel_payload | JSON | The JSON Payload of the event. |
disable_partial_success=true
query parameter to make sure that if any event in a batch fails validation, the entire request will fail.
For example: https://webhooks.us-east-2.propeldata.com/v1/WHK00000000000000000000000000?disable_partial_success=true
_propel_payload
column.
However, Propel enforces the schema for required fields. If you stop providing data for a required field that was previously unpacked into its own column, Propel will return an error.
Go to the Schema tab
Add column
Track progress
JSON Type | Propel Type |
---|---|
String | STRING |
Number | DOUBLE |
Object | JSON |
Array | JSON |
Boolean | BOOLEAN |
Null | JSON |
_propel_received_at
will be used by default.How long does it take for an event to be available via SQL or the API?