/api/applications/ID/offers/ID/notes/ID
HEAD, GET
A request with the GET verb returns information about one specific (Sticky) note on the offer record.
Syntax
GET /api/applications/123/offers/321/notes/123 Host: apply.example.edu Authorization: DREAM apikey="..."
Response headers
Content-Type: application/json Content-Length: 1234
Response codes
200 OK | The note is returned successfully |
Response example
API version >= 6
{
"created": "1970-01-01T00:00:01+00:00",
"removed": null,
"colour": "Yellow",
"pinned": false,
"collapsed": false,
"Notes": "Some comments",
}
API version < 6
"Some comments"
PUT
Update one specific offer (sticky) note.
Syntax
PUT /api/applications/123/offers/321/notes/123 Host: apply.example.edu Authorization: DREAM apikey="..."
Parameters
| Name | Description | Notes | |
|---|---|---|---|
colour | Optional | Specify the colour of the (sticky) note: Yellow, Orange, Salmon, Green, Blue, Violet | |
color | Optional | An alias for colour | [1] |
- Note [1]: If both
colourandcolorare specified, thencolouris preferred.
Raw request body
Note that the comments have to be a proper JSON string token. In a JSON string only space is allowed per the specification, newlines, for example, have to be encoded.
"Some notes\nAnother line"
Response headers
Content-Type: text/plain Content-Length: 0
Response codes
204 No Content | The note was saved |
400 Bad Request | Invalid notes. Please make sure that status is a valid JSON string with quotes. |