Can HumDay connect to opendatasoft?

Yes. HumDay reads opendatasoft's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 36 operations are documented.

Do I need to write code to automate opendatasoft?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your opendatasoft account.

What can HumDay do in opendatasoft?

1 of the 36 documented operations change something in opendatasoft, and 35 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my opendatasoft account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to opendatasoft is held behind that approval.

opendatasoft integration

What HumDay can do in opendatasoft

1 documented operations change something in opendatasoft.

PUTCreate new feedback entry./{source}/datasets/{dataset_id}/feedback

What HumDay can read from opendatasoft

These are the operations a schedule or a trigger can watch.

GETList of all pages from this portal./pages
GETAPI entry point Provides links for: catalog, your domain's list of datasets opendatasoft, all datasets on the Opendatasoft network/
GETA single page's metadata from this portal/pages/{slug}
GETEnumerate facets values for datasets and return a list of values for each facet./{source}/facets
GETList of available datasets, each with their endpoints, paginated./{source}/datasets
GETList of available metadata templates types, each with their endpoints./{source}/metadata_templates
GETEnumerate facets values for records and return a list of values for each facet./{source}/datasets/{dataset_id}/facets
GETSearch dataset's records./{source}/datasets/{dataset_id}/records
GETSource entry points Provides links for the source's datasets and metadata./{source}
GETList of available endpoints for the specified dataset, with metadata and endpoints./{source}/datasets/{dataset_id}
GETDownload file/{source}/datasets/{dataset_id}/files/{file_id}
GETRetrieve a single record based on its ID./{source}/datasets/{dataset_id}/records/{record_id}
GETList of metadata templates available for this type./{source}/metadata_templates/{metadata_template_type}
GETGet list of reuses/{source}/datasets/{dataset_id}/reuses
GETList of all snapshots for this dataset./{source}/datasets/{dataset_id}/snapshots
GETGet list of all available attachments/{source}/datasets/{dataset_id}/attachments
GETExport catalog (source) in CSV format/{source}/exports/csv
GETExport catalog (source) in RDF/XML format/{source}/exports/rdf
GETExport catalog (source) in RSS format/{source}/exports/rss
GETExport catalog (source) in TTL (turtle/rdf) format/{source}/exports/ttl
GETExport catalog (source) in XLS (Excel) format/{source}/exports/xls
GETExport catalog (source) in JSON format/{source}/exports/json
GETList of all snapshots for this dataset./{source}/datasets/{dataset_id}/snapshots/{snapshot_id}
GETExport dataset in CSV format/{source}/datasets/{dataset_id}/exports/csv
GETExport dataset in OV2 format/{source}/datasets/{dataset_id}/exports/ov2
GETExport dataset in Esri shapefile (shp) format/{source}/datasets/{dataset_id}/exports/shp
GETExport dataset in XLS (Excel) format/{source}/datasets/{dataset_id}/exports/xls
GETExport dataset in ICAL format/{source}/datasets/{dataset_id}/exports/ical
GETExport dataset in JSON format/{source}/datasets/{dataset_id}/exports/json
GETExport dataset in GEOJSON format/{source}/datasets/{dataset_id}/exports/geojson
GETRetrieve a single reuse based on its ID./{source}/datasets/{dataset_id}/reuses/{reuse_id}
GETA single metadatatemplate/{source}/metadata_templates/{metadata_template_type}/{metadata_template_name}
GETDownload attachment/{source}/datasets/{dataset_id}/attachments/{attachment_id}
GETDeprecated, use /datasets instead./{source}/aggregates
GETDeprecated, use /records instead./{source}/datasets/{dataset_id}/aggregates

How automating opendatasoft works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live opendatasoft account.
Grant access, then go live. You approve the specific opendatasoft operations it may use — and only those.

Popular opendatasoft integrations

Connect opendatasoft to the tools people pair it with most.

Automate opendatasoft with these

Questions about opendatasoft automation

Can HumDay connect to opendatasoft?: Yes. HumDay reads opendatasoft's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 36 operations are documented.
Do I need to write code to automate opendatasoft?: No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your opendatasoft account.
What can HumDay do in opendatasoft?: 1 of the 36 documented operations change something in opendatasoft, and 35 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my opendatasoft account safe?: Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to opendatasoft is held behind that approval.

Where this came from

The operations above are read from a published API description for opendatasoft at public.opendatasoft.com/api/v2/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2021-07-12.

Automate opendatasoft