Integration
Connect Colorado Information Marketplace to UUID Generator
When something happens in Colorado Information Marketplace, your agent does the next thing in UUID Generator. 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 UUID Generator 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 UUID Generator
Triggers and actions 1 trigger ยท 10 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.
Action
Find datasetsSearch 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.
Action
Find records by criteriaQuery 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.
Action
Get recordGet 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.
Action
List recordsList 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
Decode UUIDDecode an existing UUID string to extract its version, variant, and (for time-based versions) the embedded timestamp. GET https://www.uuidtools.com/api/decode/{uuid} (endpoint inferred from the site's Decode UUID tool at /decode; confirm exact path when implementing).
Action
Generate timestamp-first UUIDGenerate one or more timestamp-first (ordered) UUIDs, where the current timestamp is embedded at the start so values sort in creation order when stored/indexed. GET https://www.uuidtools.com/api/generate/timestamp-first (endpoint path per the /generate/timestamp-first docs page).
Action
Generate v1 UUIDGenerate one or more (up to 100) time-based version-1 UUIDs. GET https://www.uuidtools.com/api/generate/v1 or /v1/count/{n}.
Action
Generate v3 UUIDGenerate a deterministic version-3 (MD5-based) UUID from a namespace + name. GET https://www.uuidtools.com/api/generate/v3/namespace/{namespace}/name/{name}; namespace is ns:url|ns:dns|ns:OID|ns:X500 or a UUID; name may be base64-encoded with a base64: prefix.
Action
Generate v4 UUIDGenerate one or more (up to 100) random version-4 UUIDs. GET https://www.uuidtools.com/api/generate/v4 or /v4/count/{n}.
Action
Generate v5 UUIDGenerate a deterministic version-5 (SHA-1-based) UUID from a namespace + name. GET https://www.uuidtools.com/api/generate/v5/namespace/{namespace}/name/{name}; namespace is ns:url|ns:dns|ns:OID|ns:X500 or a UUID; name may be base64-encoded with a base64: prefix.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.