Adding message to timeline

URL: http[s]://<host>/[<prefix>/]cases/addTimelineEntry[/1.0]

If you leave out the version, the current version of the service will be called.

• case_id required String
  ID of the case to add a new timeline entry
  
  
• timeline_type required String
  type of timeline, allowed values = 'PlaintiffsTimeline', 'DefendantsTimeline'
  
  
• subject required String
  timeline entry subject
  
  
• event_date required String
  date of timeline event
  
  
• description required String
  timeline entry description
  
  
• SSO optional String
  Optional SSO token for authentication.
  
  

Allowed HTTP Methods:

• POST

Accept types:

• application/json
• application/xml
• application/x-www-form-urlencoded
• multipart/form

Accept charsets:

• UTF-8
• ISO-8859-1
• LATIN1

Output:

200 OK response type void.

4XX Client Error Response {data:<Error string>} Usually wrong usage by the client.

5XX Server Error Response {data:<Error string>} Exception, error in the service.

Additional comments:

addTimelineEntry is automatically provided using method reflection.

This service is implemented using the Albicore:SimplifiedService framework.

How to call this service:

• POST JSON in body: { "case_id":<value>, "timeline_type":<value>, "subject":<value>, "event_date":<value>, "description":<value> }
• POST urlencoded in body: case_id=<value>&timeline_type=<value>&subject=<value>&event_date=<value>&description=<value>
• POST multipart/form, encode parameters as parts.

About output:


• 200 OK All valid service executions will return OK response.
• 404 NOT FOUND Resource(s) was not found.
• 4XX error code Errors thrown indicate wrong usage.
• 500 INTERNAL ERROR Exceptions during execution.

The output is default JSON. Output can be controlled by the Accept header, set to one of the below:
• application/json for JSON format, see input description.