| PUT | /PutEmailAddress_RegRequestDate/ |
|---|
const std = @import("std");
pub const PutEmailAdd_RegResponse = struct {
success: bool = false,
already_registered: bool = false,
@"error": ?[]const u8 = null,
};
pub const PutEmailAdd_RegRequest = struct {
bpid: ?i32 = null,
email_address: ?[]const u8 = null,
};
Zig PutEmailAdd_RegRequest DTOs
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
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: application/json
Content-Type: application/json
Content-Length: length
{"BPID":0,"EmailAddress":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Success":false,"AlreadyRegistered":false,"Error":"String"}