API Documentation v2

  1. API
  2. v2

Introduction

Welcome to the Assure API.

Authorization

Our API makes use of OAuth 2 using client credentials. If you are interested in using this service, please contact us at api@myassureservices.com. We will need your account login email and a list of endpoints you would like to use.

Example Request

We recommend you use an established library to authenticate with our API. How ever it is quite simple even with out a library.

1. Make a POST request to https://app.myassureservices.com/oauth/access_token containing the following variables:

  • grant_type=client_credentials
  • client_id=<your client id>
  • client_secret=<your client secret>
2. You will get a response back containing information. If the request failed the reason why will be returned to you. If your credentials are correct you will get a response back containing the following:
  • access_token=<generated access token>
  • token_type=Bearer
  • expires_in=3600
3. Now that you have an access_token you can make requests to the API. If you wanted to view details for a hearing you send a request to the /api/v2/hearing/<hearing id> API endpoint with the following header information:
  • Authorization: Bearer <generated access token>
4. Keep in mind that your access token is only valid for the number of seconds contained in the expires_in variable that is returned to you in your authentication request. Keeping track of when your access_token expires is where a library can come in handy. You can use the same access token for all request until it expires.

Endpoints

Hearings

create

Adds a new hearing to our system.

method POST
endpoint /api/v2/hearing
return Hearing Model

Parameters

Key Type Requirement Description
client_first_name string required First name of the claimant.
client_last_name string required Last name of the claimant
client_ssn int optional SSN of the claimant. Nine digits only.
hearing_date string required Date of the hearing. MM/DD/YYYY.
hearing_time string required Time of the hearing local to hearing location and hearing date. H:MM AM/PM in 5 minute increments from 7:00 AM to 5:00 PM. 7:00 AM, 7:05 AM, 12:30 PM, 12:35 PM, etc.
location_id int required Hearing location id.
user_advocate_attending int optional The attending attorney's ID for this hearing.
suggested_attendee string optional The suggested attendee to attend this hearing.
judge_id int required The ALJ's ID for the hearing.
require_ve boolean optional Whether or not a vocational expert is required for this hearing.
require_me boolean optional Whether or not a medical expert is required for this hearing.
require_vtc boolean optional Whether or not this hearing is over video teleconference.
hearing_outcome int optional The final outcome of the hearing. 1 = Unfavorable Hearing Outcome, 2 = Partially Favorable Hearing Outcome, 3 = Favorable Hearing Outcome
note string optional Add a new note to this hearing.
initials string conditional Initials if a note is being added with this hearing.
cancelled_at string optional If the hearing was cancelled this field contains the date and time it was cancelled at. YYYY-MM-DD HH:MM:SS. You may request that the hearing be cancelled by sending this field when the hearing is not already cancelled.
candidates association optional An array containing prefered attorneys. Each entry should include the keys "user_id" (same as attorney) and "score" ranging from 0-100 representing a preference order.
external_id string optional If you have an external indentifier you'd like to keep track of for this hearing you can use this field.
skip_approval bool optional Development environment only, has no affect on live. Most edits to hearings require an approval process that delays any changes from being applied. Setting this field to 1 will make any changes get automatically approved.

update

Update an existing hearing in our system.

method PUT
endpoint /api/v2/hearing/{id}
return Hearing Model

Parameters

Key Type Requirement Description
client_first_name string required First name of the claimant.
client_last_name string required Last name of the claimant
client_ssn int optional SSN of the claimant. Nine digits only.
hearing_date string required Date of the hearing. MM/DD/YYYY.
hearing_time string required Time of the hearing local to hearing location and hearing date. H:MM AM/PM in 5 minute increments from 7:00 AM to 5:00 PM. 7:00 AM, 7:05 AM, 12:30 PM, 12:35 PM, etc.
location_id int required Hearing location id.
user_advocate_attending int optional The attending attorney's ID for this hearing.
suggested_attendee string optional The suggested attendee to attend this hearing.
judge_id int required The ALJ's ID for the hearing.
require_ve boolean optional Whether or not a vocational expert is required for this hearing.
require_me boolean optional Whether or not a medical expert is required for this hearing.
require_vtc boolean optional Whether or not this hearing is over video teleconference.
hearing_outcome int optional The final outcome of the hearing. 1 = Unfavorable Hearing Outcome, 2 = Partially Favorable Hearing Outcome, 3 = Favorable Hearing Outcome
note string optional Add a new note to this hearing.
initials string conditional Initials if a note is being added with this hearing.
cancelled_at string optional If the hearing was cancelled this field contains the date and time it was cancelled at. YYYY-MM-DD HH:MM:SS. You may request that the hearing be cancelled by sending this field when the hearing is not already cancelled.
candidates association optional An array containing prefered attorneys. Each entry should include the keys "user_id" (same as attorney) and "score" ranging from 0-100 representing a preference order.
external_id string optional If you have an external indentifier you'd like to keep track of for this hearing you can use this field.
skip_approval bool optional Development environment only, has no affect on live. Most edits to hearings require an approval process that delays any changes from being applied. Setting this field to 1 will make any changes get automatically approved.

view

Show details related to a hearing in our system.

method GET
endpoint /api/v2/hearing/{id}
return Hearing Model

list

Returns an array containing available hearings in our system.

method GET
endpoint /api/v2/hearing
return Hearing Model Collection

assign

Make a request to assign an attorney to a hearing. You can get a current list of your available attorneys by using the attorney list endpoint. If there is already an assigned attorney then the current assigned attorney will be removed and the new one provided will be assigned.

method POST
endpoint /api/v2/hearing/assign
return Basic Response

Parameters

Key Type Requirement Description
hearing_id int required Assure's ID for the hearing you would like to assign an attorney to.
attorney_id int required Assure's ID for the attorney you would like to assign.
skip_approval bool optional Development environment only, has no affect on live. Most edits to hearings require an approval process that delays any changes from being applied. Setting this field to 1 will make any changes get automatically approved.

unassign

Make a request to unassign an attorney from a hearing.

method POST
endpoint /api/v2/hearing/unassign
return Basic Response

Parameters

Key Type Requirement Description
hearing_id int required Assure's ID for the hearing you would like to remove an attorney from.

Locations

view

Show details related to a location in our system.

method GET
endpoint /api/v2/location/{id}
return Location Model

list

Returns an array containing available locations in our system.

method GET
endpoint /api/v2/location
return Location Model Collection

Judges

view

Show details related to a judge in our system.

method GET
endpoint /api/v2/judge/{id}
return Judge Model

list

Returns an array containing available judges in our system.

method GET
endpoint /api/v2/judge
return Judge Model Collection

Attorneys

view

Show details related to an attorney in our system.

method GET
endpoint /api/v2/attorney/{id}
return Attorney Model

list

Returns an array containing available attorneys in our system.

method GET
endpoint /api/v2/attorney
return Attorney Model Collection

Files

create

Uploads a file to our system and attaches it to a hearing. 200MB file size limit. Only .pdf, .doc, .docx, .png, .tiff, and .txt files are accepted.

method POST
endpoint /api/v2/file
return File Model

Parameters

Key Type Requirement Description
doc_type_id int required The doc type id for this file.
file file required File to be uploaded.
hearing_id int required The ID of the hearing this file will be attached to.

DocTypes

view

Show details related to a doc type in our system.

method GET
endpoint /api/v2/doc-type/{id}
return Doc Type Model

list

Returns an array containing available document types in our system.

method GET
endpoint /api/v2/doc-type
return Doc Type Model Collection

DocPreHearingChecklists

view

Show details related to a pre-hearing checklist in our system.

method GET
endpoint /api/v2/doc-pre-hearing-checklist/{id}
return DocPreHearingChecklist Model

Briefs

view

Show details related to a brief request in our system.

method GET
endpoint /api/v2/brief/{id}
return Brief Model

list

Returns an array containing available brief requests in our system.

method GET
endpoint /api/v2/brief
return Brief Model Collection

HearingNotes

create

Create a new note attached to a hearing. This endpoint is intended for general notes on a hearing, if you are making a hearing note containing a request to make changes to a hearing please use the hearing update endpoint with the "note" and "initials" fields to add your note to a hearing in order for hearing schedulers to review your request. If you add a note requesting changes to a hearing with this endpoint it will not notify hearing schedulers and your request may not be seen.

method POST
endpoint /api/v2/hearing-note
return HearingNote Model

Parameters

Key Type Requirement Description
hearing_id int required Assure's ID for the hearing you would like to attach the note to.
content string required The contents of the note.
initials string required Initials to use for this note. Five character limit.

list

Returns an array of HearingNote models attached to the provided hearing ID. Hearing notes are sorted by created at in descending order.

method GET
endpoint /api/v2/hearing-note
return HearingNote Model Collection

Parameters

Key Type Requirement Description
hearing_id int required Assure's ID for the hearing you want to list notes for.

ReadyToScheduleData

create

Adds a new ready to schedule hearing to our system. A RTS hearing is a hearing with no location, date or time. If a location, date and time are provided this endpoint will instead create a new hearing request.

method POST
endpoint /api/v2/ready-to-schedule-data
return ReadyToScheduleData Model

Parameters

Key Type Requirement Description
first_name string required Client's first name.
last_name string required Client's last name.
middle_name string optional Client's middle name.
hearing_request_date string optional The prefered hearing date if available. YYYY-MM-DD format.
hearing_time string optional The prefered localized hearing time if available. 11:30 AM, 2:15 PM, etc. Hearing times are only accepted in 15 min intervals from 7:00 AM to 5:00 PM
claim_type string optional The type. "TITLE 2 - DISABILITY", "TITLE 16 - DISABILITY" or "TITLE 2 AND TITLE 16 - DISABILITY" are allowed.
medical_expert string optional Whether or not a medical expert is needed. True/false or name accepted.
vocational_expert string optional Whether or not a medical expert is needed. True/false or name accepted
location_id int required Hearing location id.
judge_id int required The ALJ's (judge) ID.
external_id string optional If you have an external indentifier you'd like to keep track of for this hearing you can use this field.
external_firm_id string optional If you have an external indentifier for the firm this hearing will belong to you can use this field.
candidates association optional An array containing prefered attorneys. Each entry should include the keys "user_id" (same as attorney) and "score" ranging from 0-100 representing a preference order.

update

Update an existing ready to schedule hearing in our system.

method PUT
endpoint /api/v2/ready-to-schedule-data/{id}
return ReadyToScheduleData Model

Parameters

Key Type Requirement Description
first_name string required Client's first name.
last_name string required Client's last name.
middle_name string optional Client's middle name.
hearing_request_date string optional The prefered hearing date if available. YYYY-MM-DD format.
hearing_time string optional The prefered localized hearing time if available. 11:30 AM, 2:15 PM, etc. Hearing times are only accepted in 15 min intervals from 7:00 AM to 5:00 PM
claim_type string optional The type. "TITLE 2 - DISABILITY", "TITLE 16 - DISABILITY" or "TITLE 2 AND TITLE 16 - DISABILITY" are allowed.
medical_expert string optional Whether or not a medical expert is needed. True/false or name accepted.
vocational_expert string optional Whether or not a medical expert is needed. True/false or name accepted
location_id int required Hearing location id.
judge_id int required The ALJ's (judge) ID.
external_id string optional If you have an external indentifier you'd like to keep track of for this hearing you can use this field.
external_firm_id string optional If you have an external indentifier for the firm this hearing will belong to you can use this field.
candidates association optional An array containing prefered attorneys. Each entry should include the keys "user_id" (same as attorney) and "score" ranging from 0-100 representing a preference order.

DocPreHearingInfo

create

Submit Pre-Hearing Information for a hearing. All pre-hearing information is connected to a hearing and is used to add additional client and case rep information when a hearing requires it. In the Assure portal the pre-hearing information is displayed with other hearing information and the pre-hearing information contains fields to confirm information on the hearing is accurate. It is recommended that you also display relevant client information from the attached hearing when working with pre-hearing information and offer options for the user to update the attached hearing in the event that some client information (such as a misspelled name) does not match the information they have.

method POST
endpoint /api/v2/doc-pre-hearing-info
return DocPreHearingInfo Model

Parameters

Key Type Requirement Description
hearing_id int required Assure's hearing ID that this pre-hearing info is for.
hearing_type int required The hearing type. Options are 1 for Initial Hearing, 2 for Supplemental, 3 for Appeals Court Remanded and 4 for CDR.
case_type int required The case type. Options are 1 for Title II, 2 for Title XVI, and 3 for Concurrent.
is_client_spelling_correct int required A confirmation field required to verify the client name and SSN on file for the attached hearing match the Notice of Hearing you have.
hearing_details_match int required A confirmation field confirming all details of the attached hearing match the Notice of Hearing you have. If the hearing details do not match you will need to update the hearing via the hearing endpoints first before creating pre-hearing info. You are responsible for properly confirming all hearing details are correct when using the API.
client_phone_home string conditional The home phone number of the client. 10 digit string, numbers only. Required if no client_phone_mobile is provided.
client_phone_mobile string conditional The mobile phone number of the client. 10 digit string, numbers only. Required if no client_phone_home is provided.
client_email string optional The email of the client. Must be a valid email format if provided.
client_street string optional The street part of the clients address.
client_city string optional The city part of the clients address.
client_state string optional The 2 letter abbreviation of state part of the clients address.
client_zip string optional The zip code part of the clients address. Five digits or nine digits with a hypen. "99999" or "99999-9999".
client_ssn string required The SSN of the client.
is_outstanding_records boolean required If there are any outstanding medical records. If you are going to provide a value of "1" (for yes) you must make a call to the hearing outstanding-medical-record endpoint to create an entry for an OutstandingMedicalRecord on the hearing before saving the pre-hearing information.
special_client_circumstances string optional Any additional information for Attending Attorney e.g., does not speak English, currently hospitalized/incarcerated, etc..
case_rep_first_name string required The first name of the case rep.
case_rep_last_name string required The last name of the case rep.
case_rep_phone string required The phone number of the case rep.
case_rep_ext string optional The phone number extension of the case rep. Max 10 characters.
case_rep_email string required The email of the case rep. Must be a valid email format if provided. Use a semi-colon (;) to seperate multiple e-mail addresses. When reading this field be sure to check for semi-colons to determine if it contains more than one email.

update

Update existing pre-hearing information in our system. The ID provided should be the hearing ID the pre-hearing information is attached to. You may provide all fields with any changes or only the fields you are changing.

method PUT
endpoint /api/v2/doc-pre-hearing-info/{hearing_id}
return DocPreHearingInfo Model

Parameters

Key Type Requirement Description
hearing_id int required Assure's hearing ID that this pre-hearing info is for.
hearing_type int required The hearing type. Options are 1 for Initial Hearing, 2 for Supplemental, 3 for Appeals Court Remanded and 4 for CDR.
case_type int required The case type. Options are 1 for Title II, 2 for Title XVI, and 3 for Concurrent.
is_client_spelling_correct int required A confirmation field required to verify the client name and SSN on file for the attached hearing match the Notice of Hearing you have.
hearing_details_match int required A confirmation field confirming all details of the attached hearing match the Notice of Hearing you have. If the hearing details do not match you will need to update the hearing via the hearing endpoints first before creating pre-hearing info. You are responsible for properly confirming all hearing details are correct when using the API.
client_phone_home string conditional The home phone number of the client. 10 digit string, numbers only. Required if no client_phone_mobile is provided.
client_phone_mobile string conditional The mobile phone number of the client. 10 digit string, numbers only. Required if no client_phone_home is provided.
client_email string optional The email of the client. Must be a valid email format if provided.
client_street string optional The street part of the clients address.
client_city string optional The city part of the clients address.
client_state string optional The 2 letter abbreviation of state part of the clients address.
client_zip string optional The zip code part of the clients address. Five digits or nine digits with a hypen. "99999" or "99999-9999".
client_ssn string required The SSN of the client.
is_outstanding_records boolean required If there are any outstanding medical records. If you are going to provide a value of "1" (for yes) you must make a call to the hearing outstanding-medical-record endpoint to create an entry for an OutstandingMedicalRecord on the hearing before saving the pre-hearing information.
special_client_circumstances string optional Any additional information for Attending Attorney e.g., does not speak English, currently hospitalized/incarcerated, etc..
case_rep_first_name string required The first name of the case rep.
case_rep_last_name string required The last name of the case rep.
case_rep_phone string required The phone number of the case rep.
case_rep_ext string optional The phone number extension of the case rep. Max 10 characters.
case_rep_email string required The email of the case rep. Must be a valid email format if provided. Use a semi-colon (;) to seperate multiple e-mail addresses. When reading this field be sure to check for semi-colons to determine if it contains more than one email.

view

Show details from the pre-hearing information for a hearing in our system. The ID provided should be the hearing ID the pre-hearing information is attached to.

method GET
endpoint /api/v2/doc-pre-hearing-info/{hearing_id}
return DocPreHearingInfo Model

Data Models

Basic Response

Basic response format an API call will return.

Parameters

Key Type Description
success int Returns 1 on a successful call or 0 when we were unable to complete the request.
message string Any additional information about the request.
code int The status code returned.
data mixed Any data the request needs to return. This will be an empty value (type of empty value depends on the endpoint) if the response does not have any data to return.

Hearing

Base model of a hearing.

Parameters

Key Type Description
id int Assure's ID for this hearing.
client_first_name string First name of the claimant.
client_last_name string Last name of the claimant
client_ssn int SSN of the claimant. Nine digits only.
hearing_date string Date of the hearing. MM/DD/YYYY.
hearing_time string Time of the hearing local to hearing location and hearing date. H:MM AM/PM in 5 minute increments from 7:00 AM to 5:00 PM. 7:00 AM, 7:05 AM, 12:30 PM, 12:35 PM, etc.
owner_firm association The owning firm's information.
location_id int Hearing location id.
location association Hearing location information. Uses the location model.
user_advocate_attending int The attending attorney's ID for this hearing.
suggested_attendee string The suggested attendee to attend this hearing.
judge_id int The ALJ's ID for the hearing.
judge association The judge's information.
require_ve boolean Whether or not a vocational expert is required for this hearing.
require_me boolean Whether or not a medical expert is required for this hearing.
require_vtc boolean Whether or not this hearing is over video teleconference.
hearing_outcome int The final outcome of the hearing. 1 = Unfavorable Hearing Outcome, 2 = Partially Favorable Hearing Outcome, 3 = Favorable Hearing Outcome
note string Add a new note to this hearing.
initials string Initials if a note is being added with this hearing.
cancelled_at string If the hearing was cancelled this field contains the date and time it was cancelled at. YYYY-MM-DD HH:MM:SS. You may request that the hearing be cancelled by sending this field when the hearing is not already cancelled.
hearing_files association Files uploaded to the hearing.
doc_pre_hearing_checklist association Pre-hearing checklist attached to the hearing.
doc_medical_records association Outstanding medical record information attached to the hearing. These are created when a hearing is scheduled but more medical records are expected according to the person who completed the Pre-hearing Information. These are not actual medical record requests that are collected by a medical record provider within Assure.
contact_attempts association Contact attempts attached to the hearing.
candidates association An array containing prefered attorneys. Each entry should include the keys "user_id" (same as attorney) and "score" ranging from 0-100 representing a preference order.
external_id string If you have an external indentifier you'd like to keep track of for this hearing you can use this field.

Location

Base model of a hearing location.

Parameters

Key Type Description
id int Assure's ID for the location.
address_street_1 string Street address of the hearing location.
address_street_2 string Building number, suite, floor, etc. of the hearing location.
address_city string City of the hearing location.
address_state string State of the hearing location.
address_zip string Zip code of the hearing location.
utc_offset int UTC offset of the city where the hearing takes place. This is the offset without daylight savings in affect. e.g. -6

Judge

Base model of a hearing judge.

Parameters

Key Type Description
id int Assure's ID for this judge.
first_name string First name of the judge.
last_name string Last name of the judge.
region string The region this judge is in.
office string The office this judge works from.

Attorney

Base model of an attorney.

Parameters

Key Type Description
id int Assure's ID for this attorney.
external_id string If attorney works for your firm, you can provide an external ID for the attorney to make lookups easier on your end. If one of your attorneys is attending the hearing and you have provided an external ID, it will be listed here.
first_name string First name of the attorney attending the hearing.
last_name string Last name of the attorney attending the hearing.
is_active boolean Whether or not the attorney can log into the assure portal.
is_assignable boolean Whether or not the attorney can be assigned to new hearings.

File

Base model of a file.

Parameters

Key Type Description
id int Assure's ID for this file.
doc_type_id int The doc type id for this file.
file_type int The doc type id for this file.
size string Size of the file in bytes.
created_at date Date the file was uploaded.

DocType

Base model of a document type used by File.

Parameters

Key Type Description
id int Assure's ID for this document type.
name string The name of this document type.
description string The description of this document type.

DocPreHearingChecklist

Base model of a pre-hearing checklist.

Parameters

Key Type Description
id int Assure's ID for this pre-hearing checklist.
created_at date The date the pre-hearing checklist was created. YYYY-MM-DD HH:MM:SS.

Brief

Base model of a brief.

Parameters

Key Type Description
id int Assure's ID for the brief.
owner association The brief owner's information.
claimant_firstname string The brief claimant's first name.
claimant_lastname string The brief claimant's last name.
status_name string The brief's status.
hearing association The hearing this brief is attached to.
assigned association The brief assigned's information.
sub_assigned association The brief sub assigned's information.
brief_files association Files uploaded to the brief.
due_at string The date the brief is due. YYYY-MM-DD HH:MM:SS.
completed_at string If the brief was completed this field contains the date and time it was cancelled at. YYYY-MM-DD HH:MM:SS.

HearingNote

Base model of a hearing note.

Parameters

Key Type Description
id int Assure's ID for this hearing note.
hearing_id int Assure's ID for the hearing this note is attached to.
content string The content of the note.
initials string The initials provided by the user that created this note.
created_at string Date the note was added. YYYY-MM-DD HH:MM:SS.

HearingCandidate

Base model of a hearing candidate relation.

Parameters

Key Type Description
user_id string The user/attorneys ID.
score int The score representing a preference order.

ReadyToScheduleData

Base model of a ready to schedule hearing data.

Parameters

Key Type Description
id int Assure's id for this RTS data.
first_name string Client's first name.
last_name string Client's last name.
middle_name string Client's middle name.
hearing_request_date string The prefered hearing date if available. YYYY-MM-DD format.
hearing_time string The prefered localized hearing time if available. 11:30 AM, 2:15 PM, etc. Hearing times are only accepted in 15 min intervals from 7:00 AM to 5:00 PM
claim_type string The type. "TITLE 2 - DISABILITY", "TITLE 16 - DISABILITY" or "TITLE 2 AND TITLE 16 - DISABILITY" are allowed.
medical_expert string Whether or not a medical expert is needed. True/false or name accepted.
vocational_expert string Whether or not a medical expert is needed. True/false or name accepted
location_id int Hearing location id.
judge_id int The ALJ's (judge) ID.
external_id string If you have an external indentifier you'd like to keep track of for this hearing you can use this field.
external_firm_id string If you have an external indentifier for the firm this hearing will belong to you can use this field.
candidates association An array containing prefered attorneys. Each entry should include the keys "user_id" (same as attorney) and "score" ranging from 0-100 representing a preference order.

DocPreHearingInfo

Base model for pre-hearing info.

Parameters

Key Type Description
id int Assure's ID for this pre-hearing info.
hearing_id int Assure's hearing ID that this pre-hearing info is for.
hearing_type int The hearing type. Options are 1 for Initial Hearing, 2 for Supplemental, 3 for Appeals Court Remanded and 4 for CDR.
case_type int The case type. Options are 1 for Title II, 2 for Title XVI, and 3 for Concurrent.
is_client_spelling_correct int A confirmation field required to verify the client name and SSN on file for the attached hearing match the Notice of Hearing you have.
hearing_details_match int A confirmation field confirming all details of the attached hearing match the Notice of Hearing you have. If the hearing details do not match you will need to update the hearing via the hearing endpoints first before creating pre-hearing info. You are responsible for properly confirming all hearing details are correct when using the API.
client_phone_home string The home phone number of the client. 10 digit string, numbers only. Required if no client_phone_mobile is provided.
client_phone_mobile string The mobile phone number of the client. 10 digit string, numbers only. Required if no client_phone_home is provided.
client_email string The email of the client. Must be a valid email format if provided.
client_street string The street part of the clients address.
client_city string The city part of the clients address.
client_state string The 2 letter abbreviation of state part of the clients address.
client_zip string The zip code part of the clients address. Five digits or nine digits with a hypen. "99999" or "99999-9999".
client_ssn string The SSN of the client.
is_outstanding_records boolean If there are any outstanding medical records. If you are going to provide a value of "1" (for yes) you must make a call to the hearing outstanding-medical-record endpoint to create an entry for an OutstandingMedicalRecord on the hearing before saving the pre-hearing information.
special_client_circumstances string Any additional information for Attending Attorney e.g., does not speak English, currently hospitalized/incarcerated, etc..
case_rep_first_name string The first name of the case rep.
case_rep_last_name string The last name of the case rep.
case_rep_phone string The phone number of the case rep.
case_rep_ext string The phone number extension of the case rep. Max 10 characters.
case_rep_email string The email of the case rep. Must be a valid email format if provided. Use a semi-colon (;) to seperate multiple e-mail addresses. When reading this field be sure to check for semi-colons to determine if it contains more than one email.
created_at date The date the pre-hearing info was created. YYYY-MM-DD HH:MM:SS.