| POST | /zapier/v1/lead |
|---|
import Foundation
import ServiceStack
public class ZapierLeadRequest : Codable
{
public var title:String?
public var forenames:String?
public var surname:String?
public var companyName:String?
public var address1:String?
public var address2:String?
public var city:String?
public var county:String?
public var country:String?
public var postcode:String?
public var dateOfBirth:Date?
public var emailAddress:String?
public var homePhone:String?
public var mobilePhone:String?
public var medicalInformation:String?
public var tags:[String] = []
public var optInEmail:Bool?
public var optInSms:Bool?
required public init(){}
}
public class ZapierLeadResponse : Codable
{
public var memberId:Int?
public var memberKey:String?
public var created:Bool?
required public init(){}
}
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.
POST /zapier/v1/lead HTTP/1.1
Host: api.clubmanagercentral.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"Title":"String","Forenames":"String","Surname":"String","CompanyName":"String","Address1":"String","Address2":"String","City":"String","County":"String","Country":"String","Postcode":"String","DateOfBirth":"0001-01-01T00:00:00.0000000","EmailAddress":"String","HomePhone":"String","MobilePhone":"String","MedicalInformation":"String","Tags":["String"],"OptInEmail":false,"OptInSms":false}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"MemberId":0,"MemberKey":"00000000000000000000000000000000","Created":false}