| PUT | /customers/{customerId}/noticeprograms/{programId}/noticetypes/{id} | Updates an existing notice type for the given customer's given notice program. Fails if this user does not have access to this customer or if the notice type or notice program doesn't exist. |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | path | Guid | Yes | The notice program id |
| CustomerId | path | Guid | Yes | The customer id |
| ProgramId | path | int | Yes | The notice program id |
| Name | body | string | Yes | The label to show, or the reason. |
| IsActive | body | bool | Yes | Whether the notice type is active (available) or not. |
| Sequence | body | int | No | This notice type's place in the seqence of other notice types within a notice program. |
| Hiatus | body | int | Yes | The length, in days before another notice should be issued. |
| IsRealTimeNotice | body | bool | No | Whether or not this notice type is a 'real-time' synchronized notice (i.e. events about it are sent between data partners as they happen). |
| IsEmailableNotice | body | bool | No | Whether or not this notice type is emailable (i.e. email our partner when a notice of this type happens). |
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 /customers/{customerId}/noticeprograms/{programId}/noticetypes/{id} HTTP/1.1
Host: api.paylock.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"id":0,"customerId":"00000000000000000000000000000000","programId":0,"name":"String","isActive":false,"sequence":0,"hiatus":0,"isRealTimeNotice":false,"isEmailableNotice":false}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length 0