eQuipAPI

FindDlmsNotificationMappings

Returns Configure Dlms Notification details; requires a valid user to complete this request

The following routes are available for this service:
POST	/dlms/notifications/mappings	Returns a dlms Notifications confuration details.
GET	/dlms/notifications/mappings	Returns a dlms Notifications confuration details.

**FindDlmsNotificationMappings** Parameters:
Name	Parameter	Data Type	Required	Description
UserID	query	Guid	Yes	The UserID that authorizes the caller to complete the request. Contact your eQuip admin.
take	body	int	No	The number of requisitions to return. 0 returns all entries.
skip	body	int	No	The page offset to start retrieving data. 0 returns first page entries.
sort	body	IEnumerable<Sort>	No	The collection of field and direction to sort requisitions
filter	body	Filter	No	The parameters collection to filter requisitions

**Sort** Parameters:
Name	Parameter	Data Type	Required	Description
Field	body	string	No
Dir	body	string	No

**Filter** Parameters:
Name	Parameter	Data Type	Required
Field	body	string	No
Operator	body	string	No
Value	body	Object	No
Logic	body	string	No
Filters	body	IEnumerable<Filter>	No

**DataSourceResultResponse** Parameters:
Name	Parameter	Data Type	Required
Data	body	IEnumerable	No
Total	body	int	No
IncludeLinkTotal	body	int	No
Aggregates	body	Object	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

HTTP + JSON

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

POST /json/reply/FindDlmsNotificationMappings HTTP/1.1 
Host: equipstage3.e-isg.com 
Content-Type: application/json
Content-Length: length

{"UserID":"String","take":0,"skip":0,"filter":{"field":"String","operator":"String","value":{},"logic":"String"}}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Total":0}