Integration
Connect jo4.io to District of Columbia Open Data
When something happens in jo4.io, 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 jo4.io 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 jo4.io and District of Columbia Open Data
Triggers and actions 1 trigger · 10 actions
Trigger
New URL CreatedTriggers when a new short link is created in your jo4 account.
Action
Add referral programCreates a referral programme in jo4.io, setting how referrers are rewarded and how its sign-up page looks.
Action
Add short URLShortens a web address into a jo4.io link, with optional preview details, tracking, scheduling, password protection and app deep links.
Action
Get referral leaderboardReturns the referrers on a referral programme, ranked by how much they have brought in.
Action
Get short URLReturns one short link from your jo4.io account, with the address it points to and the details held against it.
Action
Get short URL statsReturns how a short link has performed: total clicks and page views, broken down by device, browser, country, city, referrer, language and campaign.
Action
List short URLsReturns the short links in your jo4 account, optionally with their click statistics.
Action
Update short URLChanges an existing jo4.io short link — its destination, preview details, tracking, scheduling, password protection or app deep links.
Action
Find datasetsSearch the DC Open Data catalog for datasets by keyword, category, or tag, returning matching dataset ids, titles, and descriptions.
Action
Find recordsQuery a dataset's features/records with attribute filters, spatial filters, sorting, and paging, returning JSON or GeoJSON results.
Action
Get datasetGet 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.
Each app on its own
Reviews