Retrieve TCGA CDEs verbatim, i.e in FireBrowse Beta

What this operation does

Retrieve TCGA CDEs verbatim, i.e.

• GETReads data · Samplesfirebrowse.org/Samples/Clinical

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 FireBrowse Beta 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 FireBrowse Beta operations

• Retrieve list of all TCGA patientsGET · reads data
• Retrieve names of all columns in the mutation annotation filesGET · reads data
• Retrieve dates of all GDAC Firehose stddata & analyses runsGET · reads data
• Retrieve miRSeq dataGET · reads data
• Retrieve sample countsGET · reads data
• Retrieve mRNASeq dataGET · reads data
• Retrieve links to summary reports from Firehose analysis runsGET · reads data
• Obtain identities of TCGA consortium member centersGET · reads data

All 30 FireBrowse Beta operations

Questions

Can HumDay retrieve tcga cdes verbatim, i.e in FireBrowse Beta?

Yes. This operation is published in FireBrowse Beta'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 FireBrowse Beta account?

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

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 FireBrowse Beta account.

Where this came from

Read from a published API description for FireBrowse Beta at firebrowse.org/api/api-docs. The description above is the provider’s own wording, not ours. Last published 2019-07-25.