ClubReady Api

CreateProspectRequestV2

The following routes are available for this service:
POST	/v2/{ApiKey}/club/{StoreId}/prospect	(obsolete) Create a Prospect

**CreateProspectRequestV2** Parameters:
Name	Parameter	Data Type	Required	Description
XForwardedFor	header	string	No	IP address of the end user
ApiKey	query	string	Yes	Api Key - grants access to resources
StoreId	query	integer	Yes	ClubReady Club ID (StoreID internally)
FirstName	query	string	Yes	First Name
LastName	query	string	Yes	Last Name
Email	query	string	Yes	Email Address
Gender	query	string	No	Gender
Address	query	string	No	Address
City	query	string	No	City
State	query	string	No
Zip	query	string	No
Phone	body	string	No
WorkPhone	body	string	No
DateOfBirth	body	DateTime?	No
CellPhone	body	string	No
AddPackageId	query	integer	No	Specify a Package to apply to the new prospect
ProspectTypeId	query	integer	No	Specify a specific Prospect Type for the new prospect
ReferralTypeId	query	integer	No	Specify a specific Referral Type for the new prospect
SendEmail	query	boolean	Yes	Send a Welcome email to the new prospect
EmailTemplateId	query	integer	No	Only used if SendEmail = True
Coupon	query	string	No
Note	query	string	No	Add an internal note for the new prospect
RestrictedId	body	int?	No
RestrictedResourceType	body	RestrictedResourceType	No

**CreateProspectRequestV2Dto** Parameters:
Name	Parameter	Data Type	Required
FirstName	form	string	No
LastName	form	string	No
Address	form	string	No
City	form	string	No
State	form	string	No
Zip	form	string	No
Email	form	string	No
Gender	form	string	No
AddPackageId	form	int?	No
ProspectTypeId	form	int?	No
ReferralTypeId	form	int?	No
SendEmail	form	bool	No
Phone	form	string	No
WorkPhone	form	string	No
DateOfBirth	form	DateTime?	No
CellPhone	form	string	No
Coupon	form	string	No
Note	form	string	No
EmailTemplateId	form	int?	No

**ApiDtoBase** Parameters:
Name	Parameter	Data Type	Required
ApiKey	form	string	No
StoreId	form	int?	No
ChainId	form	int?	No

**RestrictedResourceType** Enum:
Store
Chain
User
Undefined

To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv

HTTP + JSV

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /v2/{ApiKey}/club/{StoreId}/prospect HTTP/1.1 
Host: www.clubready.com 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	XForwardedFor: String,
	ApiKey: String,
	StoreId: 0,
	FirstName: String,
	LastName: String,
	Email: String,
	Gender: String,
	Address: String,
	City: String,
	State: String,
	Zip: String,
	Phone: String,
	WorkPhone: String,
	DateOfBirth: 0001-01-01,
	CellPhone: String,
	AddPackageId: 0,
	ProspectTypeId: 0,
	ReferralTypeId: 0,
	SendEmail: False,
	EmailTemplateId: 0,
	Coupon: String,
	Note: String,
	RestrictedId: 0,
	RestrictedResourceType: Store,
	ChainId: 0
}