Create court locations and court cases in ServeManager and link them to a job
domain: servemanager.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate via HTTP Basic Auth with the API key
POST /api/courts with type:'court', branch_name, county, and a nested address_attributes object to register a court location, capturing the returned court id
POST /api/court_cases with type:'court_case', plaintiff, defendant, number, filed_date/court_date, and court_id to link the case to that location
GET /api/court_cases?q= to text-search existing cases by case number, plaintiff, defendant, or court branch name before creating a duplicate
Pass the resulting court_case_id into POST /api/jobs so the job inherits the case's court and party details
GET /api/court_cases?company_id= to list all cases associated with a given client or process-server company
Known gotchas
filed_date and court_date must be plain ISO 8601 dates without a time component, unlike the datetime fields used elsewhere in the API
Sending the wrong type value ('court' vs 'court_case') on either endpoint produces a 409 Conflict rather than a descriptive field-level error
Creating a court_case without a known court_id leaves the court object null on the response — job creation proceeds silently without court metadata rather than erroring
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?