Requires the role: | Admin |
GET,OPTIONS | /R_RegistrationCustomFields | ||
---|---|---|---|
GET,OPTIONS | /R_RegistrationCustomFields/{Ids} | ||
GET,OPTIONS | /R_RegistrationCustomFields/RegistrationId/{RegistrationId} | ||
GET,OPTIONS | /R_RegistrationCustomFields/UnitId/{UnitId} | ||
GET,OPTIONS | /R_RegistrationCustomFields/AccountId/{AccountId} |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Ids | path | List<long> | No | |
RegistrationId | path | long? | No | |
UnitId | path | string | No | |
AccountId | path | 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
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /json/reply/R_RegistrationCustomFields HTTP/1.1
Host: regapi.pumpalarm.com
Content-Type: application/json
Content-Length: length
{"Ids":[0],"RegistrationId":0,"UnitId":"String","AccountId":0}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length [{"RegistrationId":0,"CustomFieldName":"String","CustomFieldValue":"String","Id":0}]