EDI - Hearing Create

date

Yes*

Date

hearing date
hrg date

Dates tend to be the hardest part for users to get right. Pay special attention to the formats. 

The dates must be formatted like the following:

MM/dd/yy H:mm

Please note: the "H" signifies the use of a 24-hour clock (aka military time).

Example: 10/31/2020 14:00

fileNumber

Yes

String

account number
file number
file no
file #
jst file

Your internal file number, usually from your case management system.

time

Yes*

Date

If you cannot submit the date and time in the date column above, then you may break it down into two parts using this field. Use the date field above for just the month, day, and year portion given the same formats as above. Just omit the hours and minutes from the date column. Then put the hours and minutes into this column using the formats above. The importer will basically combine the two fields with a space between and process as one field.

Please note: You must provide both a date and time for your hearings. However, if you can combine the date & time fields (see example above), you do not need to provide an additional field with the time.

state

Yes

String

court state
court_state
st

2-letter postal abbreviation, or written out in full.

county

Yes*

String

Name matching list on website; No word "county" needed in value.

If you do not provide this, we must be able to deduce the county from the courtName value given.

courtName

Yes 

String

court location

The court description. Usually, "Circuit Court" or "District Court". Our system will do a best guess match for the actual court location based on this information. 

customLocation

No

Boolean

If the hearing is being held at a location other than a court, set this value to: TRUE to add a customer location

locationName 

No

String

For use with Custom Location only. The name of the custom location, i.e. building name, etc.

locationAddress

No

String

For use with Custom Location only.  Address of the custom location.

locationCity

No

String

For use with Custom Location only.  City of custom location

locationZipCode

No

String

For use with Custom Location only.  Zip code of the custom location.

caseNumber

Yes

String

case number
case_number
case #

Case number recognized by the court.

caseName

Yes*

String

case_title

Case caption (X vs. Y). However, a few clients do not have that readily available, so that you may use the "plaintiff" and "defendant" fields instead. The system will concatenate these together with "vs." between them to build a caseName for you.

clientName

Yes

String

Name of who you are representing.

serviceId

No

String

32-character ID of the hearing type (service) to use. To find this value, login to the website and press Resources on the home page. You will see a price list there. If you are enabled for data transfer, the service IDs will appear as the final column in the table.

You may also use the full name of the service but this is not recommended. The unique service ID will never change however the name might due to categorization updates.

If you do not give us a serviceId, we will try and make the best guess.

echo

No

String

hearing type

Short name for hearing type (service) as it exists in your case management system.  
This will require initial setup to create a 1:1 connection from your terms to how they relate to Docketly service types.  

attorney

No

String

The name of the attorney that is handling this case at your firm.

instructions

No

String

hearing notes

The special instructions field that should be shown to the covering attorney.

If you have multiple columns of data that constitute the instructions, our import can join them into one field for you. You may use the field names of instructions2, instructions3, instructions4, and instructions5. They will all be appended together in the numerical order.
LONGTEXT: large character limit.

comments

No

String

The public comments that will be shown to attorneys we offer the hearing to.
LONGTEXT: large character limit.

zone

No

String

This is the timezone of the given hearing date field. If not provided, the system will use the local time of the court. Do not use unless you know what you are doing.

plaintiff

No

String

creditor
plaintiff name

Name of the plaintiff.

defendant

No

String 

debtor name
cm name
def's name

Name of the defendant. 

opposingCounsel

No

String

Opposing counsel name

Name of opposing counsel

dateAnswered

No

Date

Formatted as "yyyy-MM-dd" or "M/d/yyyy"

dateComplaintFiled

No

Date

Formatted as "yyyy-MM-dd" or "M/d/yyyy"

dateDefaulted

No

Date

Formatted as "yyyy-MM-dd" or "M/d/yyyy"

dateServed

No

Date

Formatted as "yyyy-MM-dd" or "M/d/yyyy"

contact

No

String

Who to contact at the hearing in case of an issue. If not given, it will default to the primary user on the account.

contactPhone

No

String

How to contact the contact above at the hearing in case of an issue. Format phone number as (XXX) XXX-XXXX. If not given, it will default to the primary user on the account.

user.username

No

String

Without this value, the hearing will be imported as the master user in your firm. You can use this field to override. The value is the username (what you use to login to Docketly) of the user for whom the hearing should be associated with.

isCriminalBackgroundRequired

No

Boolean

Use "true" to indicate you would like to require securing an attorney with an annually verified seven-year nationwide criminal background check free from a felony conviction or a misdemeanor conviction involving a financial crime. Extra fees may apply. 

isInsuranceRequired

No

Boolean

Use "true" to indicate you would like to require securing an attorney that maintains legal malpractice insurance or is covered under Docketly's insurance policy.

isSeekArrestWarrant

No

Boolean

Use "true" to indicate you would like the covering attorney to seek an arrest warrant. The default is "false" if not specified.

isSeekBodyAttachment

No

Boolean

Use "true" to indicate you would like the covering attorney to seek a body attachment. The default is "false" if not specified.

isSeekRuleToShowCause

No

Boolean

Use "true" to indicate you would like the covering attorney to see a Rule To Show Cause. The default is "false" if not specified.

isServed

No

Boolean

Use "true" to specify the opposing party has been served. Use "false" to specify non-service on the opposing party. Do not include if the service is pending or is not required.

balance

No

Decimal

The total balance of what the defendant owes your client, including principal, interest, costs, fees, etc.

interest

No

Decimal

The amount of interest incurred.

principal

No

Decimal

Principal balance of costs owed.

attorneyCosts

No

Decimal

The attorney fees being asked for.

courtCosts

No

Decimal

The total of the court costs owed.

miscCosts

No

Decimal

Any additional costs that need to be communicated.

attorneySelected.email

No

String

If using an in-house attorney and you have your account set up as such, you may specify the email address of the in-house attorney to have the hearing auto-covered by that attorney when you post the hearing.

judge

No

String

If you know it, you can provide the judge's name. "Last, First" is the preferred format.

department

No

String

A specific sub-division within the court. Different names are used in each state in our user interface, but the data is stored as a department. We only support in some states. Test via our new hearing form for the latest supported states. Some supported states include CA, MO (Division), NY (Part), WA.

isTelephonic

No

Boolean

Use "true" to indicate the hearing can be done telephonically.

forwarder

No

String

Name of the forwarder.

attorneyPhone

No

String

Attorney's phone number into the hearing data for the covering attorney to call if need be.

url

No

String

The url for telephonic/remote hearings.

telephonicMethod

No

String

The remote method, i.e. Zoom, CourtCall, etc.

coverageInstructions

No

String

Telephonic/remote details, i.e. meeting ID, etc.

telephonicPhone

No

String

Phone number for telephonic hearings.