Get Contact information for plaintiff or representatives, if present.

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

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

• case_id required String
  Undocumented method parameter.
  
  
• index optional Integer
  null or 0 is the plaintiff contact, 1 or 2 is the plaintiff representative contact.
  
  
• 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 Contact:

• address String
• postcode String
• city String
• region String
• country String
• comment String (Additional custom contact information field.)
• email String
• phone String
• fax String
• website String
• linkedin String
• facebook String
• instagram String
• twitter String
• other String
• id int (Database Primary key)
• client boolean (Whether this contact represent someones client.)
• company boolean (Whether this contact represent a company.)
• self_employed boolean (Whether this contact represent a person that is self employed.)
• company_name String (Company name should be provided if company is true.)
• orgnr String (Organisation Number, usually a global identifier.)
• first_name String
• middle_name String
• last_name String
• date_of_birth String (Zulu time of birth)
• gender String (Optional gender, 'male', 'female'.)

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:

getCasePlaintiffContact 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> }
• POST urlencoded in body: case_id=<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.