Tenant Server V1

post_pm_ticketList

The following routes are available for this service:
All Verbs	/post_pm_ticketList

**post_pm_ticketList** Parameters:
Name	Parameter	Data Type	Required
token	query	string	Yes
tokensecret	query	string	Yes
email	query	string	Yes
type	query	string	No

**post_pm_ticketListResponse** Parameters:
Name	Parameter	Data Type	Required
result	form	int	No
message	form	string	No
ticketResponsible	form	List<string>	No
billingResponsible	form	List<string>	No
ticketCC	form	List<string>	No
billingCC	form	List<string>	No
postTicketCC	form	List<string>	No
postTicketResponsible	form	List<string>	No
tenantProductRequest	form	List<string>	No
postEvent	form	List<postEventUser>	No
list	form	List<TicketInfo>	No

**postEventUser** Parameters:
Name	Parameter	Data Type	Required
email	form	string	No
xview	form	bool	No
xadd	form	bool	No
xdel	form	bool	No

**TicketInfo** Parameters:
Name	Parameter	Data Type	Required
idwebcare1	form	string	No
tenantname	form	string	No
premiseaddress	form	string	No
tenantphone	form	string	No
tenantemail	form	string	No
vendorschedule	form	string	No
username	form	string	No
firstname	form	string	No
lastname	form	string	No
location	form	string	No
priority	form	string	No
description	form	string	No
idcia	form	string	No
idproject	form	string	No
idtenant	form	string	No
status	form	string	No
address	form	string	No
creaby	form	string	No
creadate	form	DateTime	No
acknowledgedate	form	DateTime	No
archivedate	form	DateTime	No
followup	form	string	No
assignpm	form	string	No
assignto	form	string	No
assignemail	form	string	No
projectname	form	string	No
city	form	string	No
zipcode	form	string	No
latitude	form	string	No
longitude	form	string	No
tenantdba	form	string	No
list	form	List<attachmentFile>	No
category	form	categoryInfo	No

**attachmentFile** Parameters:
Name	Parameter	Data Type	Required
fileName	form	string	No
base64	form	string	No
base64Thumbnail	form	string	No

**categoryInfo** Parameters:
Name	Parameter	Data Type	Required
idnumber	form	string	No
description	form	string	No
category	form	string	No

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 /jsv/reply/post_pm_ticketList HTTP/1.1 
Host: sdk.lovettcommercial.com 
Content-Type: text/jsv
Content-Length: length

{
	token: String,
	tokensecret: String,
	email: String,
	type: String
}

HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	result: 0,
	message: String,
	ticketResponsible: 
	[
		String
	],
	billingResponsible: 
	[
		String
	],
	ticketCC: 
	[
		String
	],
	billingCC: 
	[
		String
	],
	postTicketCC: 
	[
		String
	],
	postTicketResponsible: 
	[
		String
	],
	tenantProductRequest: 
	[
		String
	],
	postEvent: 
	[
		{
			email: String,
			xview: False,
			xadd: False,
			xdel: False
		}
	],
	list: 
	[
		{
			idwebcare1: String,
			tenantname: String,
			premiseaddress: String,
			tenantphone: String,
			tenantemail: String,
			vendorschedule: String,
			username: String,
			firstname: String,
			lastname: String,
			location: String,
			priority: String,
			description: String,
			idcia: String,
			idproject: String,
			idtenant: String,
			status: String,
			address: String,
			creaby: String,
			creadate: 0001-01-01,
			acknowledgedate: 0001-01-01,
			archivedate: 0001-01-01,
			followup: String,
			assignpm: String,
			assignto: String,
			assignemail: String,
			projectname: String,
			city: String,
			zipcode: String,
			latitude: String,
			longitude: String,
			tenantdba: String,
			list: 
			[
				{
					fileName: String,
					base64: String,
					base64Thumbnail: String
				}
			],
			category: 
			{
				idnumber: String,
				description: String,
				category: String
			}
		}
	]
}