| POST | /zapier/v1/lead |
|---|
export class ZapierLeadResponse
{
public MemberId?: number;
public MemberKey?: string;
public Created?: boolean;
public constructor(init?: Partial<ZapierLeadResponse>) { (Object as any).assign(this, init); }
}
export class ZapierLeadRequest
{
public Title?: string;
public Forenames?: string;
public Surname?: string;
public CompanyName?: string;
public Address1?: string;
public Address2?: string;
public City?: string;
public County?: string;
public Country?: string;
public Postcode?: string;
public DateOfBirth?: string;
public EmailAddress?: string;
public HomePhone?: string;
public MobilePhone?: string;
public MedicalInformation?: string;
public Tags?: string[];
public OptInEmail?: boolean;
public OptInSms?: boolean;
public constructor(init?: Partial<ZapierLeadRequest>) { (Object as any).assign(this, init); }
}
TypeScript ZapierLeadRequest DTOs
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
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: text/jsv
Content-Type: text/jsv
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-01,
EmailAddress: String,
HomePhone: String,
MobilePhone: String,
MedicalInformation: String,
Tags:
[
String
],
OptInEmail: False,
OptInSms: False
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
MemberId: 0,
MemberKey: 00000000000000000000000000000000,
Created: False
}