PUT | /api/services/{ServiceGuid} | Update the Contact and Company info of a service |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ServiceGuid | path | Guid | Yes | |
ContactName | body | string | No | |
ContactEmail | body | string | No | |
ContactPhoneNumber | body | string | No | |
CompanyName | body | string | No | |
CompanyAddress | body | string | No | |
CompanyCity | body | string | No | |
CompanyStateProvince | body | string | No | |
CompanyZipPostalCode | body | string | No | |
CompanyCountry | body | string | No | |
CompanyWebsite | body | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ResponseStatus | form | ResponseStatus | 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.
PUT /api/services/{ServiceGuid} HTTP/1.1
Host: api.secure-messaging.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{
"serviceGuid": "00000000000000000000000000000000",
"contactName": "String",
"contactEmail": "String",
"contactPhoneNumber": "String",
"companyName": "String",
"companyAddress": "String",
"companyCity": "String",
"companyStateProvince": "String",
"companyZipPostalCode": "String",
"companyCountry": "String",
"companyWebsite": "String"
}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length { "responseStatus": { "errorCode": "String", "message": "String", "stackTrace": "String", "errors": [ { "errorCode": "String", "fieldName": "String", "message": "String", "meta": { "String": "String" } } ], "meta": { "String": "String" } } }