| POST | /zapier/v1/lead |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Title | body | string | No | |
| Forenames | body | string | No | |
| Surname | body | string | No | |
| CompanyName | body | string | No | |
| Address1 | body | string | No | |
| Address2 | body | string | No | |
| City | body | string | No | |
| County | body | string | No | |
| Country | body | string | No | |
| Postcode | body | string | No | |
| DateOfBirth | body | DateTime? | No | |
| EmailAddress | body | string | No | |
| HomePhone | body | string | No | |
| MobilePhone | body | string | No | |
| MedicalInformation | body | string | No | |
| Tags | body | string[] | No | |
| OptInEmail | body | bool | No | |
| OptInSms | body | bool | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| MemberId | form | int | No | |
| MemberKey | form | Guid | No | |
| Created | form | bool | No |
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}