Can HumDay connect to Lumminary?

Yes. HumDay reads Lumminary'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 Lumminary?

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

What can HumDay do in Lumminary?

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

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

Automate Lumminary

HumDay reads Lumminary’s own published API description and derives 17 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

Automate Lumminary

What Lumminary is

# Introduction The Lumminary API was built to allow third parties to interact with Lumminary customers and gain access to their genetic data. The Lumminary API is fast, scalable and highly secure. All requests to the Lumminary API take place over SSL, which means all communication of Customer data is encrypted. Before we dive in, some definitions. This is what we mean by: |Term|Definition| |------

API host: api.lumminary.com

What HumDay can do in Lumminary

6 documented operations change something in Lumminary.

POSTGeneral-purpose authentication/auth/jwt
POSTProvide a file result to the authorization, e/products/{productId}/authorizations/{authorizationId}/file
POSTSignal that processing is complete, without uploading any result/products/{productId}/authorizations/{authorizationId}
POSTGet a large group of SNPs/clients/{clientId}/datasets/{datasetId}/snps/
POSTProvide a result for the authorization/products/{productId}/authorizations/{authorizationId}/credentials
POSTCatch-all Authorization state, for authorizations that passed all verifications and should reach the partner Product, but cannot be fulfilled for various reasons/products/{productId}/authorizations/{authorizationId}/unfulfillable

What HumDay can read from Lumminary

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

GETReference genome builds/reference/genomes/
GETGet product details/products/{productId}
GETReference SNP data/reference/snps/{snpAccession}
GETReference genome metadata/reference/genomes/{genomeBuildAccession}/chromosomes
GETSequence for a region of the reference genome/reference/genomes/{genomeBuildAccession}/chromosomes/{chromosomeAccession}
GETGeneric gene information/reference/genes/databases/{databaseName}/accessions/{accession}
GETGet SNP information/clients/{clientId}/datasets/{datasetId}/snps/{snpId}
GETGet gene by symbol/clients/{clientId}/datasets/{datasetId}/genes/{geneSymbol}
GETRead authorizations/products/{productId}/authorizations
GETRead authorizationId/products/{productId}/authorizations/{authorizationId}
GETRead snps/clients/{clientId}/datasets/{datasetId}/snps/

How automating Lumminary 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 Lumminary account.
Grant access, then go live. You approve the specific Lumminary operations it may use — and only those.