Create a ServeManager job with a client company, court case, and an attached document to be served via the ServeManager API
domain: servemanager.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with HTTP Basic Auth using your ServeManager API key as the username and an empty password (verify with GET /api/account)
Create or look up a client company via POST or GET /api/companies to obtain a client_company_id
Optionally create a court_case via POST /api/court_cases, linking a court_id obtained from POST /api/courts
POST /api/jobs with type:'job', client_company_id, and a documents_to_be_served_attributes array; set external_url so ServeManager fetches a hosted file, or omit it to receive a short-lived put_url per document
If using the two-step upload, PUT the raw file bytes to the returned put_url immediately after job creation, before it expires
Track status via job_status/service_status fields on subsequent GET /api/jobs/:id calls or via webhooks instead of polling aggressively
Known gotchas
Content-Type: application/json is mandatory on POST/PUT or the API returns 406; URL-encoded bodies return 409 instead of a field-level validation error
The put_url for local file uploads is short-lived (documented as accessible for about 1 hour after job creation) so uploads must happen immediately, not queued for later
job.servemanager_job_number (the human-facing ID) is different from job.id (internal reference) — ServeManager's own docs warn never to display job.id to users
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?