Integration
Connect Colorado Information Marketplace to Postali
When something happens in Colorado Information Marketplace, your agent does the next thing in Postali. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Colorado Information Marketplace and Postali to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Colorado Information Marketplace and Postali
Triggers and actions 1 trigger · 12 actions
Trigger
New recordPolling trigger: fires when a new row appears in a specified Colorado Information Marketplace (Socrata SODA API) dataset. GET https://data.colorado.gov/resource/{dataset_id}.json ordered by a rowid/created/updated system field ($order=:id DESC or an updated_at column) with $limit, dedup by the row's system id (:id) or an updated_at watermark since datasets vary in whether they expose a stable update timestamp column.
- Find datasets
Search the Colorado Information Marketplace open-data catalog for datasets by keyword/category. GET https://data.colorado.gov/api/catalog/v1?q={query}&limit=... (Socrata Discovery API) returning dataset id, name, description, category, and update timestamps. Used to locate the dataset identifier that other ops (List/Get/Find records) require as input.
- Find records by criteria
Query a Colorado Information Marketplace (Socrata SODA API) dataset with a SoQL $where/$select/$order filter. GET https://data.colorado.gov/api/v3/views/{dataset_id}/query.json (or resource/{dataset_id}.json on older SODA2 endpoints) with SoQL query params ($where, $select, $order, $limit, $offset). Requires the dataset identifier (8-char alphanumeric, e.g. ydr8-5enu) as input plus the SoQL clauses.
- Get record
Get a single row from a Colorado Information Marketplace (Socrata SODA API) dataset by its row identifier. GET https://data.colorado.gov/resource/{dataset_id}/{row_id}.json (or a $where=:id='{row_id}' query when the dataset has no explicit row identifier). Requires dataset_id and row_id.
- List records
List all rows in a Colorado Information Marketplace (Socrata SODA API) dataset, paginated. GET https://data.colorado.gov/resource/{dataset_id}.json with $limit/$offset params. Requires the dataset identifier (8-char alphanumeric, e.g. ydr8-5enu).
Action
Find postal codes in bulkBatch lookup of multiple postal codes in one call. POST /api/v1/{country}/bulk — send a list of codes, get back the per-code results (same shape as Get postal code).
- Find postal locations by query
Fuzzy search over settlement names, municipalities, and postal codes for a country. GET /api/v1/{country}/search?q=...&limit=. Useful for autocomplete.
- Get municipality
Get detail for one municipality identified by state + municipality path segments. GET /api/v1/{country}/municipio/{estado}/{municipio}.
- Get postal code
Look up a postal code (CP) for a country (mx/co/es). GET /api/v1/{country}/cp/{codigo} — returns estado, municipio, and all asentamientos (settlements) tied to the code.
- Get state
Get detail (with totals) for one state/department/province by slug. GET /api/v1/{country}/estado/{slug}.
- List municipalities
List municipalities belonging to a given state, by state slug. GET /api/v1/{country}/estado/{slug}/municipios.
- List states
List level-1 administrative divisions (states/departments/provinces) for a country, with precomputed totals. GET /api/v1/{country}/estados.
- Validate postal code
Quick validation of a postal code — returns whether it exists and how many asentamientos it covers, without the full list. GET /api/v1/{country}/validate/{codigo}. Useful for checkout form gating.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.