Search Accela Construct API records by type, status, and date range using the Search Records endpoint
domain: developer.accela.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Build a JSON body for POST /v4/search/records with criteria such as module, type (with a value property), openedDateFrom, openedDateTo, and address
Send the request with an access token, since Search Records is a POST-based query rather than the simple GET /v4/records/{ids} lookup
Use the expand query parameter (e.g. expand=addresses,contacts) to include related sub-objects in the response without extra calls
Paginate results using the standard offset/limit response envelope returned by the search
For narrower lookups by known IDs, prefer GET /v4/records/{ids} instead, since it is a lighter no-auth-eligible call for that specific case
Known gotchas
Search Records is a distinct POST /v4/search/records endpoint from Get All Records (GET /v4/records) and Get Records (GET /v4/records/{ids}); criteria syntax differs between them
Date criteria such as openedDateFrom/openedDateTo accept specific formats (e.g. 2013-01-01 or 2013-01-01 00:00:00) and must match exactly or the search silently returns no matches
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?