Integration
Connect DNSFilter to District of Columbia Open Data
When something happens in DNSFilter, your agent does the next thing in District of Columbia Open Data. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want DNSFilter and District of Columbia Open Data 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 DNSFilter and District of Columbia Open Data
Triggers and actions 4 triggers ยท 10 actions
Trigger
Blocked Page Form SubmittedTriggers when a user submits the form on the blocked page.
- Blocked Page Visited
Triggered when someone in your DNSFilter account hits a blocked page.
- Invoice Available
Triggered when a new DNSFilter invoice becomes available.
- Policy Changed
Triggered when a DNSFilter policy is created or changed.
- Add to Allow List
Adds a single domain to a DNSFilter policy's allow list, with a note explaining why.
- Add to Block List
Adds a single domain to a DNSFilter policy's block list, with a note explaining why.
- Allow Category in a Policy
Allows a content category in a DNSFilter policy by taking it off that policy's blocked-category list.
- Assign Policy to a Roaming Client
Assigns a DNSFilter policy to a roaming client, so that device filters against that policy.
- Assign Policy to a Site
Assigns a DNSFilter policy to a site, so traffic from that site filters against that policy.
- Block Category in a Policy
Blocks a content category in a DNSFilter policy by adding it to that policy's blocked-category list.
- Create Site
Creates a new site (network) in DNSFilter, optionally on a chosen policy and block page.
Action
Find datasetsSearch the DC Open Data catalog for datasets by keyword, category, or tag, returning matching dataset ids, titles, and descriptions.
- Find records
Query a dataset's features/records with attribute filters, spatial filters, sorting, and paging, returning JSON or GeoJSON results.
- Get dataset
Get a dataset's metadata and field/schema definitions by dataset or layer id, so callers know what attributes can be filtered or returned.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.