/*
* Zernio API
*
* API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal. Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema). Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id.
*
* The version of the OpenAPI document: 1.523.0
* Contact: support@zernio.com
* Generated by: https://openapi-generator.tech
*/
use crate::models;
use serde::{Deserialize, Serialize};
/// WebhookPayloadAnalyticsSynced : Webhook payload for `analytics.synced`. Fired once per connected account each time its analytics sync cycle completes successfully. Poll-driven (roughly hourly per account), not real-time, and never fired for a skipped or failed cycle. A TRIGGER, not a transport: it deliberately carries no metrics and no cursor. When it arrives, call `GET /v1/analytics/delta` with YOUR OWN last `nextCursor` to read what changed, across every account, in one paginated stream. **Why there is no cursor.** The feed's ordering position is assigned inside the analytics store when the row is materialized, which normally happens after this event fires. A cursor minted here could sit ahead of the rows the event announces and make you skip them. Your own `nextCursor` never can. Because of the same lag, a delta read issued the instant this event lands can legitimately come back empty. That is not \"nothing changed\": poll again with the same cursor you last used rather than treating the account as done. **Use a DEDICATED webhook endpoint.** This event is high volume (roughly one delivery per connected account per hour), and a subscription's consecutive-failure count is shared across all its events. An outage while it flows can suppress the low-volume publishing events on the same subscription.
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct WebhookPayloadAnalyticsSynced {
/// Stable webhook event ID: the dedupe key, also sent as the X-Zernio-Event-Id header and identical on every retry and redelivery. It identifies the event only, never an account or other resource.
#[serde(rename = "id")]
pub id: String,
/// The profiles this event belongs to, each with the externalId you set on it (null when none is set). Use it to route the event to your tenant without storing Zernio profile ids. Present on every event tied to a profile, absent on events that belong to none. Events spanning several profiles (a post published to accounts of different profiles) list each once.
#[serde(rename = "profiles", skip_serializing_if = "Option::is_none")]
pub profiles: Option<Vec<models::WebhookProfilesInner>>,
/// Always true when present: only a sample sent by POST /v1/webhooks/test with an event carries it. Real deliveries never do.
#[serde(rename = "test", skip_serializing_if = "Option::is_none")]
pub test: Option<bool>,
#[serde(rename = "event")]
pub event: Event,
#[serde(rename = "account")]
pub account: Box<models::WebhookPayloadAnalyticsSyncedAccount>,
#[serde(rename = "sync")]
pub sync: Box<models::WebhookPayloadAnalyticsSyncedSync>,
/// UTC time at which Zernio generated this event (set once when the event payload is built, before delivery is queued).
#[serde(rename = "timestamp")]
pub timestamp: String,
}
impl WebhookPayloadAnalyticsSynced {
/// Webhook payload for `analytics.synced`. Fired once per connected account each time its analytics sync cycle completes successfully. Poll-driven (roughly hourly per account), not real-time, and never fired for a skipped or failed cycle. A TRIGGER, not a transport: it deliberately carries no metrics and no cursor. When it arrives, call `GET /v1/analytics/delta` with YOUR OWN last `nextCursor` to read what changed, across every account, in one paginated stream. **Why there is no cursor.** The feed's ordering position is assigned inside the analytics store when the row is materialized, which normally happens after this event fires. A cursor minted here could sit ahead of the rows the event announces and make you skip them. Your own `nextCursor` never can. Because of the same lag, a delta read issued the instant this event lands can legitimately come back empty. That is not \"nothing changed\": poll again with the same cursor you last used rather than treating the account as done. **Use a DEDICATED webhook endpoint.** This event is high volume (roughly one delivery per connected account per hour), and a subscription's consecutive-failure count is shared across all its events. An outage while it flows can suppress the low-volume publishing events on the same subscription.
pub fn new(
id: String,
event: Event,
account: models::WebhookPayloadAnalyticsSyncedAccount,
sync: models::WebhookPayloadAnalyticsSyncedSync,
timestamp: String,
) -> WebhookPayloadAnalyticsSynced {
WebhookPayloadAnalyticsSynced {
id,
profiles: None,
test: None,
event,
account: Box::new(account),
sync: Box::new(sync),
timestamp,
}
}
}
///
#[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)]
pub enum Event {
#[serde(rename = "analytics.synced")]
AnalyticsSynced,
}
impl Default for Event {
fn default() -> Event {
Self::AnalyticsSynced
}
}