Automate OpenTrials

What HumDay can read from OpenTrials

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

• GETReturns trials based on a search query./search
• GETReturns list of sources/sources
• GETReturns document categories/document_categories
• GETSearch the FDA documents/search/fda_documents
• GETReturns details of a document/documents/{id}
• GETReturns a trial's raw record from its sources/trials/{trialId}/records/{id}
• GETReturns documents/documents
• GETReturns a trial's raw records from its sources/trials/{id}/records
• GETReturns FDA applications/fda_applications
• GETAutocomplete search feature for supported database entities (location)./search/autocomplete/{in}
• GETReturns a trial's details and related entities (e.g./trials/{id}
• GETReturns person details/persons/{id}
• GETReturns condition details/conditions/{id}
• GETReturns publication details/publications/{id}
• GETReturns intervention details/interventions/{id}
• GETReturns organisation details/organisations/{id}
• GETReturns an FDA application details/fda_applications/{id}

How automating OpenTrials works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. 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.
3. See it proven. The program runs and shows you the result before it is allowed near your live OpenTrials account.
4. Grant access, then go live. You approve the specific OpenTrials operations it may use — and only those.

Automate OpenTrials with these

• Monarchinitiative BioLink164 operations
• UniCourt Enterprise158 operations
• OSF APIv2 Documentation156 operations
• IllumiDesk143 operations
• Figshare136 operations
• MCW Rat Genome Database100 operations
• U.S. EPA Enforcement and Compliance History Online (ECHO) Detailed Facility Report (DFR)94 operations
• OpenFEC91 operations
• NBA Stats83 operations
• Thebluealliance The Blue Alliance65 operations
• eDRV57 operations
• Collegefootballdata College Football Data51 operations

Categories

• Open data

Questions about OpenTrials automation

Can HumDay connect to OpenTrials?

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

Do I need to write code to automate OpenTrials?

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 OpenTrials account.

What can HumDay do in OpenTrials?

0 of the 17 documented operations change something in OpenTrials, and 17 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my OpenTrials 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 OpenTrials is held behind that approval.

Where this came from

The operations above are read from a published API description for OpenTrials at raw.githubusercontent.com/opentrials/api/master/api/swagger/swagger.yaml. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.