| PUT | /PutEmailAddress_RegRequestDate/ |
|---|
#![allow(
dead_code,
non_camel_case_types,
non_snake_case,
clippy::upper_case_acronyms
)]
use serde::{Deserialize, Serialize};
use serde_json::Value;
use std::collections::HashMap;
#[derive(Serialize, Deserialize, Debug, Clone, PartialEq, Default)]
#[serde(default)]
pub struct PutEmailAdd_RegResponse {
pub success: bool,
#[serde(rename = "alreadyRegistered")]
pub already_registered: bool,
#[serde(default, skip_serializing_if = "Option::is_none")]
pub error: Option<String>,
}
#[derive(Serialize, Deserialize, Debug, Clone, PartialEq, Default)]
#[serde(default)]
pub struct PutEmailAdd_RegRequest {
#[serde(default, skip_serializing_if = "Option::is_none")]
pub bpid: Option<i32>,
#[serde(rename = "emailAddress")]
#[serde(default, skip_serializing_if = "Option::is_none")]
pub email_address: Option<String>,
}
Rust PutEmailAdd_RegRequest DTOs
To override the Content-type in your clients, use the HTTP Accept Header, append the .csv suffix or ?format=csv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
PUT /PutEmailAddress_RegRequestDate/ HTTP/1.1
Host: webservices.mbukdatabase.co.uk
Accept: text/csv
Content-Type: text/csv
Content-Length: length
{"BPID":0,"EmailAddress":"String"}
HTTP/1.1 200 OK
Content-Type: text/csv
Content-Length: length
{"Success":false,"AlreadyRegistered":false,"Error":"String"}