Registrar Web Services

R_CreateRegistrationRequest

**Requires Authentication**
Required role:	Admin

The following routes are available for this service:
POST	/R_CreateRegistrationRequest
OPTIONS	/R_CreateRegistrationRequest

**R_CreateRegistrationRequest** Parameters:
Name	Parameter	Data Type	Required
UnitId	body	string	No
ProductId	body	long	No
DeviceId	body	string	No
DeviceSerialNumber	body	string	No
CellularProfileId	body	long	No
PcbSerial	body	string	No
BoardFirmwareVersion	body	string	No
RadioFirmwareVersion	body	string	No
BrandId	body	long	No
ElligibleBundleId	body	long?	No
ResellerId	body	long?	No
CustomFields	body	Dictionary<string, string>	No
Validate	body	bool	No
Id	body	long	No

**BaseAdminRequest** Parameters:
Name	Parameter	Data Type	Required	Description
Requester	form	string	No	Identity of the caller

**R_CreateRegistrationResponse** Parameters:
Name	Parameter	Data Type	Required	Description
RegistrationId	form	long	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/R_CreateRegistrationRequest HTTP/1.1 
Host: regapi.pumpalarm.com 
Content-Type: application/json
Content-Length: length

{"UnitId":"String","ProductId":0,"DeviceId":"String","DeviceSerialNumber":"String","CellularProfileId":0,"PcbSerial":"String","BoardFirmwareVersion":"String","RadioFirmwareVersion":"String","BrandId":0,"ElligibleBundleId":0,"ResellerId":0,"CustomFields":{"String":"String"},"Validate":false,"Id":0,"Requester":"String"}

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

{"RegistrationId":0}