/*
* 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.104.0
* Contact: support@zernio.com
* Generated by: https://openapi-generator.tech
*/
use crate::models;
use serde::{Deserialize, Serialize};
/// CreateInboxConversationRequestHeaderLocation : WhatsApp only. Required to send a template whose approved header format is LOCATION: Meta only accepts the location's lat/long at send time, never at template creation, so there is nothing to fill in automatically. Cannot be combined with headerMedia (a template has exactly one header).
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct CreateInboxConversationRequestHeaderLocation {
/// Latitude in decimal degrees.
#[serde(rename = "latitude")]
pub latitude: f64,
/// Longitude in decimal degrees.
#[serde(rename = "longitude")]
pub longitude: f64,
/// Location name shown to the recipient (e.g. a business name).
#[serde(rename = "name", skip_serializing_if = "Option::is_none")]
pub name: Option<String>,
/// Location address shown to the recipient.
#[serde(rename = "address", skip_serializing_if = "Option::is_none")]
pub address: Option<String>,
}
impl CreateInboxConversationRequestHeaderLocation {
/// WhatsApp only. Required to send a template whose approved header format is LOCATION: Meta only accepts the location's lat/long at send time, never at template creation, so there is nothing to fill in automatically. Cannot be combined with headerMedia (a template has exactly one header).
pub fn new(latitude: f64, longitude: f64) -> CreateInboxConversationRequestHeaderLocation {
CreateInboxConversationRequestHeaderLocation {
latitude,
longitude,
name: None,
address: None,
}
}
}