Returns a trial's details and related entities in OpenTrials

What this operation does

Returns a trial's details and related entities (e.g.

• GETReads data · trialsopentrials.local/trials/{id}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which OpenTrials operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other OpenTrials operations

• Returns trials based on a search queryGET · reads data
• Returns list of sourcesGET · reads data
• Returns document categoriesGET · reads data
• Search the FDA documentsGET · reads data
• Returns details of a documentGET · reads data
• Returns a trial's raw record from its sourcesGET · reads data
• Returns documentsGET · reads data
• Returns a trial's raw records from its sourcesGET · reads data

All 17 OpenTrials operations

Questions

Can HumDay returns a trial's details and related entities in OpenTrials?

Yes. This operation is published in OpenTrials's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Does this change anything in my OpenTrials account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in OpenTrials.

Do I need to write code?

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

Where this came from

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