Guide for Developers (Bioinformatics Experts)

The App Market API enables quick integration of your apps into Sequencing.com App Market. 

Use this API to sell your app in Sequencing.com's App Market while continuing to host your app on your own site.

• The user’s genetic data is processed using your systems/infrastructure.
• The App Market API is simple and it's just about 3 calls between Sequencing.com and your system.
• We are developer friendly and provide you with API plugins, a secure integration environment and a convenient development console so you can test and trace while implementing the API.

Benefits

• Requires limited development effort.
• Your app can be available for sale in the App Market in a few days.
• Your app instantly becomes universally compatible with all genetic data formats.
  • Without any coding effort on your part, your app will instantly be compatible with genetic data from almost any source including whole genome sequencing, exome sequencing, 23andMe (all versions), Ancestry.com (all versions), Family Tree DNA (all versions), National Geographic (all versions), and many other genetic testing provides.
  • You no longer have to worry about data file compatibility. As new data formats are released, Sequencing.com will seamlessly enable new data formats to be compatible with your app.
• Your app obtains access to Sequencing.com’s large user base that is growing at an incredibly fast rate.
• Your app becomes part of a centralized market for apps powered by genetic data.
• Your app benefits from the marketing and PR initiatives of Sequencing.com

The App Market API is designed to be quick, easy and painless for you to integrate into your site. 

When you use the API, this is what will occur at Sequencing.com

• Your app is marketed and sold in Sequencing.com’s App Market

• When a user purchases your app, your app will be added to the user’s My Apps page along with a ‘Start’ button. The user can then use your app at any time.

• When user clicks ‘Start,’ the user will be able to select a genetic data file stored in his or her Sequencing.com account.
  • You can also have the option to have the user provide non-genetic information, such as data your app requires. This can be any non-genetic information such as the user's age, gender, BMI, height, weight, etc.

• Sequencing.com will send your system a secure API call letting your system know that a user has submitted a genetic data file for processing that will include :
  • security authentication
  • identification of the app
  • identification of the app user
  • secure access to the app user’s genetic data
  • any non-genetic information provided by the user (optional)

• Sequencing.com will preprocess the genetic data so that when you receive it, the data is already compatible with your system. This includes:
  • the specific format your system requires to process the genetic data (such as genomeVCF, 23andMe txt, csv, etc.)   learn more about selecting your system's optimal genetic data format
    • the user's genetic data can also be sent to your system via JSON, which is similar to 23andMe's API.
  • the specific subset of genetic data that your software is configured to process

This is what will occur at your site

• The user’s genetic data is processed using your current system.

• When the results are ready, your system will send an API call to Sequencing.com letting us know that the user’s data has been successfully processed. The results will be sent back to Sequencing.com using the API.

• The user is notified that the results are ready.

• The user signs into her or his Sequencing.com account to view the results of your app.

The Monetization Dashboard provides you with real-time sales statistics so you can easily monitor your sales and royalties.

You can also view all payments sent to you from Sequencing.com and easily modify the method by which you receive your monthly payments.

View the Monetization Dashboard demo

Sequencing.com provides PCI-compliant payment processing for your app. You are able to not only set the sales price for your app but also determine the sales terms.

• Important consideration: A large percentage of Sequencing.com users have more than one genetic data file in their account, such as a single account that contains the genetic data for each family member. This is important to take into consideration when selecting the sales terms.

Sales Terms

• Price Per File
  • User is charged the app's sales price any time the user starts the app with a genetic data file that has not been previously processed by that app.
  • Example: If a user pays for File A and File B to be processed by your app, the user will be charged your app's sales price for both File A and File B. If in the future the user starts your app with File A again, the user will not be charged for this app job because File A was already processed by that specific app.

• Price Per Use
  • User is charged the app's sales price each time the user starts the app.
  • Example: If a user pays for File A to be processed by your app, the user will be charged your app's sales price for File A. If in the future the user starts your app with File A again, the user will be charged again.

• Price Per App
  • Unlimited: User is charged a single upfront price for your app and can then use the app an unlimited number of times. The app never expires.
  • Limited Time Only: User is charged a single upfront price for your app and can then user the app an unlimited number of times within a specific length of time.
    • You determine the time period, which can be any length of time. The most popular is three months. After the time period, the app will expire from the user's account and the user will have to re-purchase your app.
  • Limited Use Only: User is charged a single upfront price for your app and can then use the app up to a maximum amount without time limitation.
    • You determine the amount of usage. After the app is used the maximum amount, the app will expire from the user's account and the user will have to re-purchase your app.
  • Limited Time & Use (Mixed): User is charged a single upfront price for your app and can then use the app up to a maximum amount with a time limitation.
    • You determine both the time period and the amount of usage. After the app is used the maximum amount OR if the time period is reached, the app will expire from the user's account and the user will have to re-purchase your app.

Special Terms

The Special Terms below can be added to any of the Pricing Terms above. These Special Terms enable you to provide an incentive for the user to experience your app. 

• Introductory Pricing
  • User is charged an introductory price for a limited amount of time or uses. Once the time or usage threshold is reached, the user is thereafter charged your app's standard sales price.
    • You determine the introductory price as well as the time period and/or the maximum number of usage allowed.
    • Example: A user purchases your app and is charged $10 for the first use. After the first use, the user is then charged $20 thereafter whenever that app is used.

• Free Trial
  • User can use your app for free during a limited amount of time or uses. Once the time or usage threshold is reached, the user is thereafter charged your app's standard sales price.
    • Example: A user purchases your app and can use the app once for free. After the first use, the user is then charged $20 thereafter whenever that app is used.

• You implement the App Market API and your app is added to Sequencing.com's App Market.

• You provide your app's assets (company logo, app icon, app description, visuals such as images or videos, etc.) to Sequencing.com and specify your app's sales price and terms of sale.

• Once the App Market API has been implemented, a user can view and purchase your app in Sequencing.com’s App Market.

• After purchasing your app, the user can use your app at any time simply by signing into his or her Sequencing.com account.

• When the user starts your app, the user selects a genetic data file stored in his or her Sequencing.com account.
  • Sequencing.com provides your app with Universal Compatibility with all genetic data formats from all genetic testing technologies. This includes everything from whole genome sequencing data to consumer genetic testing services such as AncestryDNA and 23andMe.
  • In addition to genetic data, the user can also provide non-genetic information such as the user’s age, gender, BMI, height, weight, etc.
    • You determine what non-genetic information, if any, is necessary for the user to provide so that your app(s) processes successfully.
  • Sequencing.com will ask the user to provide this information when the user starts your app and will then securely transmit this information to your system using the App Market API.

• Sequencing.com sends your system an API call letting your system know that a user has submitted a genetic data file for processing that will include the following (discussed in detail in the API Specifications section below):
  • security authentication
  • identification of the app
  • identification of the app user
  • access to the app user’s genetic data
  • any non-genetic information provided by the user (optional)

• Using the API call above, Sequencing.com sends your system the user’s genetic data (along with any non-genetic information your app needs) and your app processes the data. Processing of the data is performed using your system's current workflow.
  • You determine the file format of the genetic data that Sequencing.com will make available to your system.
    • Regardless of the format of the data stored in the user's Sequencing.com account, our Universal Genetic Data Compatibility technology will provide genetic data to your system in any format that is compatible with your system. Adding your app to Sequencing.com's App Market makes your app instantly compatible with all genetic data formats.
      • Example 1: User has whole genome sequencing data as paired FASTQ files but your system is only configured to process 23andMe v4 data. Our Universal Genetic Data Compatibility technology instantaneously makes the user's data available to your system in 23andMe v4 format. You can even choose to receive the genetic data as a 23andMe-compatible CSV file or via 23andMe-compatible JSON streaming.
      • Example 2: User has AncestryDNA data but your system is only configured to process VCF files. When this user uses your app, the user's genetic data is made instantly available to your system in VCF format.

• When the app results are ready, your system sends an API response to Sequencing.com letting our system know that the user’s data has been successfully processed and that the results are ready for the user to view. This will include (discussed in detail in this document):
  • security authentication
  • identification of the app
  • identification of the app user
  • url (to your site) for the app user to access the results (optional)
  • a copy of the results, such as a pdf, html file or a png/jpg (optional)

• Sequencing.com notifies the user that the app results are ready and provides guidance for accessing the results. The user views the app results either at your site or at Sequencing.com or both. It's your choice.
  • User accesses the app results at your site.
    • This is usually accomplished by providing the user with a url that includes a token. We can also provide the user with a url to your site and a username and temporary password (both generated by your system and provided to the user when Sequencing.com notifies him or her that the app results are ready).
  • For optimal UX, the API also allows your system to send the app results to Sequencing.com as a pdf, html file(s) or image file(s). These files are then securely stored in the user's Sequencing.com account for free and forever (ie they never expire).
    • The the user will then be able to access, share, download or delete the results at any time.
  • Alternatively, some dvelopers perfer for the app results to only be accessible via Sequencing.com. If you prefer this approach, simply configure the API to only send the results as a file to Sequencing.com without providing a URL that the user can use to access the results to your site. (Discussed in the documentation below.)

To add your apps to Sequencing.com's App Market:

1) Read the App Market API documentation below.

2) Submit a Support Request stating that you want to become a Registered Developer.^*

3) Once you become a Registered Developer, you'll receive access to Sequencing.com's private integration environment called JEDI.

4) Use the Development Console at JEDI to test your endpoints.

5) Once your endpoints are working, we'll add your apps to JEDI's private App Market. This will allow you to test the entire workflow end-to-end in an actual (but private) App Market.

6) Only after you approve your apps in the JEDI App Market will we deploy your apps to the publically accessible App Market at Sequencing.com (ie our production site).

^*Please note that you cannot access JEDI, use JEDI's Development Console or proceed forward with implementing the App Market API until you contact Support. Our Support Team will send you additional resources for using the App Market API as well as Sequencing.com's Registered Developer Agreement.

Becoming a Registered Developer allows you to access JEDI and proceed forward with adding your apps to Sequencing.com's App Market by implementing the App Market API.

Sequencing.com's provides registered developers with access to a dedicated, secure integration environment called JEDI.

JEDI includes a Development Console, which enables you to test your integration of the App Market API. Using JEDI, you'll also be able to view your app and perform end-to-end testing of your app(s) in a private App Market that is not accessible by the public.

Once the integration is complete and you approve your app appearance in the App Market, your app will be ready for launch in Sequencing.com's production App Market.

JEDI Integration Environment: https://jedi.sequencing.com

Use the Development Console's Job Submission Test to receive demo genetic data via the App Market API.

All HTTP endpoints described in this section should be located on your side and invoked by Sequencing.com servers.

All requests that are sent to endpoints by Sequencing.com servers contain following HTTP headers.

Description: This is endpoint that needs to be implemented by your system

Purpose: Provides your system with data needed for processing.

This endpoint should be secured and accessed by using the token we sent to your system in a request described in Section 1.1.1 above

Request body payload specification

• Data format: JSON
• Method: POST

Request header specification

Invocation example

Note: The dataFileId, masterFileId and userId used below are for example purposes only. They are not active and will not work. Please contact Support to become a Registered Developer. You will then receive active data for these fields to use during your development and integration.

$ curl -XPOST -H "Content-Type: application/json" -H "Authorization: Bearer <authenticationToken>" --data '{"sequencingJobId":123, "applicationId":10, "dataFileId":"efce558e-3237-4805-b03d-7d182b569679 ", "masterFileId":"9f7202ce-9316-49bf-8eb4-0ea99538f664", "userId":"36A16A2505369E0C922B6EA7A23A56D2", "attributes":{"Age":"36","Ethnicity":"White","Gender":"Male","Height":"163","Weight":"70"​}' https://www.somewhere.com/external/sequencing/job/register

where <authenticationToken> should present token to access your system's endpoint.

Response body payload specification

• Data format: JSON

When implementing the App Market API, you'll indicate to Sequencing.com's Onboarding Team what genetic data format is most optimal for your system to process. We'll then configure the App Market API so that whenever a user purchases your app, the user's data will always be provided in the data format your system is already optimized for. 

• You can select to receive a user's genetic data in almost any format including gVCF, VCF, Clinical+ VCF, 23andMe data file, 23andMe JSON API, Ancestry.com data file, BAM, FASTQ, etc. 
  • Example: Your system is already configured to process 23andMe v4 data files.
    • You'll indicate this to the Sequencing.com Onboarding Team so that whenever your apps are used, Sequencing.com will send the user's data to your system in 23andMe v4 format.
    • Even if the user has selected a FASTQ or BAM file as the input file for your app, Sequencing.com will instantly send you the data in 23andMe v4 format.
      • Sequencing.com's Universal Genetic Data Compatibility enables your app to instantly become compatible with all genetic data formats.
        • This allows you to focus on creating the best possible apps while Sequencing.com handles the complexities and ensuring your app is always compatible with all data formats.

​Purpose

This required endpoint provides your system with the ability to securely obtain the user's genetic data.

Request specification

Data format: octet-stream

Method: GET

URI (Integration Environment): https://jedi-data.sequencing.com/File/Download

URI (Production Environment): https://data.sequencing.com/File/Download

Request parameters

HTTP headers

Invocation examples

Note: The id and Authorization Token used below are for example purposes only. They are not active and will not work. Please contact Support to become a Registered Developer and obtain an active Authorization Token.

1) Source format (VCF or 23andme depending on what format ou indicate is most optimal for your system)

$ curl -XGET 'https://data.sequencing.com/File/Download?id=89e929b7-0c8e-4a1d-951d-917ebee5ef64' -H "Authorization: Bearer SSESS4595a8c94ea23d8eae6124e5b5819d9b|1zFZ0uEhREFw5xbE8BbAONFmJTUO6NJN2IdaIqsdvlE|8D266E6A-2BA8-4ECC-896B-328CCAAF014D" -v -o result.vcf

2) JSON format with data in response body

$ curl -XGET 'https://data.sequencing.com/File/Download?id=89e929b7-0c8e-4a1d-951d-917ebee5ef64&json=1' -H "Authorization: Bearer SSESS4595a8c94ea23d8eae6124e5b5819d9b|1zFZ0uEhREFw5xbE8BbAONFmJTUO6NJN2IdaIqsdvlE|8D266E6A-2BA8-4ECC-896B-328CCAAF014D" -v

Output example:

{
  "rs4477212": "AA",
  "rs3094315": "AA",
  "rs3131972": "GG",
  "rs12124819": "AA"
}

3) JSON format as a downloadable content

$ curl -XGET 'https://data.sequencing.com/File/Download?id=89e929b7-0c8e-4a1d-951d-917ebee5ef64&json=1&file=1' -H "Authorization: Bearer SSESS4595a8c94ea23d8eae6124e5b5819d9b|1zFZ0uEhREFw5xbE8BbAONFmJTUO6NJN2IdaIqsdvlE|8D266E6A-2BA8-4ECC-896B-328CCAAF014D" -v -o result.json

4) JSON format as a downloadable content compressed with gzip

$ curl -XGET 'https://data.sequencing.com/File/Download?id=89e929b7-0c8e-4a1d-951d-917ebee5ef64&json=1&file=1&compressed=1' -H "Authorization: Bearer SSESS4595a8c94ea23d8eae6124e5b5819d9b|1zFZ0uEhREFw5xbE8BbAONFmJTUO6NJN2IdaIqsdvlE|8D266E6A-2BA8-4ECC-896B-328CCAAF014D" -v -o result.json.gz

where <sequencingAuthenticationToken> should present a token to access the endpoint on Sequencing.com that is acquired during authentication without brackets (refer to Section 1.1.1 for more details).

Example 1

Your system starts processing data.

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":0}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

Example 2

Your system finishes processing with error due to inability to download the user's genetic data file from Sequencing.com.

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":1, "completionStatus": 2}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

Example 3

Your system encounters an unknown error during app job processing that causes the app to stop (ie the app is unable to continue processing the user's data).

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":1, "completionStatus": 1, "errorMessage":"Error or exception specification"}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

Example 4

Your system has successfully finished processing (ie your app completes processing the user's data) and sends two base64 encoded PDF reports (without callback URL).

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":1, "completionStatus": 0, "outputFilesContents": {"Result1":"base64encodedPDF","Result2":"base64encodedPDF"}}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

Example 5

Your system successfully finished processing and sends both base64 encoded PDF and callback URL with token.

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":1, "completionStatus": 0, "callback": {"url":"https://www.somewhere.com/external/sequencing/callback?refid=cb02a3723424ff1b0be1d53fba5b6c2207a6017c"}, "outputFilesContents": {"Result1":"base64encodedPDF"}}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

Example 6

Your system has successfully finished processing and sends one downloadable PDF report using results URL (without callback URL).

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":1, "completionStatus": 0, "outputFiles": {"Result":"https://www.somewhere.com/0/1/223/result.pdf"}}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

Example 7

Your system has successfully finished processing and sends two downloadable PDF reports using two results URLs (without callback URL).

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":1, "completionStatus": 0, "outputFiles": {"Melanoma risk result":"https://www.somewhere.com/0/1/223/result1.pdf", "Vitamin D result":"https://www.somewhere.com/0/2/334/result2.pdf"}}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

where <sequencingAuthenticationToken> should present a token to access endpoint on Sequencing.com that is acquired during authentication without brackets (refer to Section 1.1.1 for more details).

Example 8

Your system has successfully finished processing and sends callback URL only (without providing PDF report).

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":1, "completionStatus": 0}, "callback": {"url":"https://www.somewhere.com/external/sequencing/callback?refid=cb02a3723424ff1b0be1d53fba5b6c2207a6017c"}}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

Example 9

Your system has successfully finished processing and sends the callback URL with dynamically generated username and password.

Sequencing.com will convey this Callback URL along with the username and password to the user and user will use this to login to your site to obtain access to app job results. This example applies only if a Callback URL is included while a Downloadable Copy of Results File URL is not included.

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":1, "completionStatus": 0}, "callback": {"url":"https://www.somewhere.com/external/sequencing/callback", "username": "5cpo07", "password": "x7hetra#3EBavah" }}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

Example 10

Your system has successfully finished processing and sends both callback URL with token and pdf report using results URL.

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":1, "completionStatus": 0, "callback": {"url":"https://www.somewhere.com/external/sequencing/callback?refid=cb02a3723424ff1b0be1d53fba5b6c2207a6017c"}, "outputFiles": {"Result":"https://www.somewhere.com/0/1/223/result.pdf"}}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

Example 11

Your system has successfully finished processing and sends callback URL with username and password and pdf report using results URL.

$ curl -XPOST -H "Content-Type: application/json" --data '{"sequencingJobId":123, "status":1, "completionStatus": 0, "callback": {"url":"https://www.somewhere.com/external/sequencing/callback", "username": "5cpo07", "password": "x7hetra#3EBavah"}, "outputFiles": {"Result":"https://www.somewhere.com/0/1/223/result.pdf"}}' https://api.sequencing.com/v1/TpUpdateExternalJob?apiKey=<sequencingAuthenticationToken>

Code innovative bioinformatics-related apps by leveraging the Sequencing.com platform.

Yes. Say if you had dataset of several BAM files and if you wanted to convert them into Genome VCF or VCF files and if you had to change the reference genome files as a part of your workflow, then you would probably have to create custom scripts and run the script each time. In addition you would have to monitor the progress and in addition make sure the files pass the QC process. Now you may leave all that to sequencing.com. For e.g. our UGENE app, which is also available on sequencing.com app store, each functionality in the app can be used via an API. So in your code you would call the API for the UGENE app, passing in the correct parameters and in some time you will get the correctly formatted file. File storage, app execution and monitoring and notifications all happens on the sequencing.com platform at no cost to you. In addition call the APIS as much as you like, whenever you like and from any device that you like.

The Sequencing.com platform provides you API access to apps that are coded by our expert team members conforming to the standards in adherence to the literature.  Access the API 24x7, run your code, store your data and also make your app available as APIs for other developers to use.

The instructions below are for submitting an app to Sequencing.com's App Market.

• You own your code and we host your app on our platform, which means we take care of marketing, security, cloud computing resources, bandwidth and payment processing.

You may also use our API and App Chain technology to add Real-Time Personalization to apps on any platform, including iOS, Android and web. After adding Real-Time Personalization to your app, submit a Support Request and we'll include information about your app in the Sequencing.com App Market.

To submit an app, open a Support Request and select I want to submit my app.

Please include the following details in your request:

1. Name of app
2. Do you want Sequencing.com to host your app on our platform?
3. Coding language your app is written in
4. Is there a UI component to your app?
   • If yes, is there a prototype?
5. What does your app do?
6. What is the output of your app? (HTML, PHP, JSON, PDF, GFF3, SVG, CSV, etc.)
7. Who will be the likely users of your app? (Individuals, Bioinformaticians, Researchers, Healthcare Professionals, etc?)

You do not need to submit actual code with this initial request. After submitting your request, a member of our A-Team (App Team) will contact you to further discuss your app.

Your app will under the system privileges setup for running all apps. If your app requires any special configuration such as increased memory then you may do so in your code i.e. code based memory management. If, however, you require system wide settings, you may contact us.

We support several views for data. You may choose to show your data in a table that supports paging, sorting and a very advanced search. We also support line, bar or pie chart. If your data is a list of multimedia resources then you could also use our multimedia module to display data. We also support PDF viewers so you may choose to display data in PDF viewer. Your code will be responsible for generating the PDF.  For all modules except for the PDF files the data should be returned in JSON format. For PDF documents a URL will be generated and shown on the UI.

Once you upload your app into our App Store, our team of experts will install your app and manage the QC process. Once everything checks out, you will receive a notification from us when your app is available in the app store for other developers.

Once you have coded your app it can be deployed and released to the world.

If you would like to make your app available to the world in Sequencing.com' App Market:

1. Submit a Support Request to be connected to our On-boarding Team
2. Review the documentation below for implementing the App Market API, which includes drop-in code that will allow you to quickly connect your system to Sequencing.com's App Market

To add your app to Sequencing.com's App Market, submit a Support Request or email dev@sequencing.com.

Sequencing.com's free App Market API enables your app to have all the benefits of being sold in Sequencing.com's App Market while leveraging the system and website you've already build.

Best if you’ve already created a unique backend system for processing genetic data and a frontend for providing results via a user interface.

When a user purchases your app, Sequencing.com will automatically and securely send your system that's user's genetic data.

• We'll pre-process the user's genetic data so that when you receive it, 

  • it's in the format your system already uses

  • it's the specific dataset required for your software to process

• We'll redirect the user to your site so that the user integrates directly with your site, uses your current UI, etc.

Detailed Overview

Benefits of selling your app in Sequencing.com's App Market

• Join the largest global marketplace for apps powered by genetic data. 

• Gain access to Sequencing.com's large and rapidly growing community.

• Become instantly data agnostic so that users who have had genetic testing from any provider are now your potential customers

  • your app will instantly be able to accept data from almost any source including whole genome sequencing, exome sequencing, Helix, 23andMe (all versions), Ancestry.com (all versions), Family Tree DNA (all versions), National Geographic - The Genographic Project (all versions), Genes for Good and many others.

  • you no longer have to worry about genetic data compatibility. As new data formats are released, Sequencing.com will seamlessly enable these new formats to be compatible with your app.

• Acquire awareness and adoption by leveraging Sequencing.com's marketing and user acquisition expertise.

Using an IDE of your choice you may code your app. RTP technology can be coded into apps that are available via any platform or OS, including iOS, Android, Mac OS, Windows and almost all distros of Linux.

Access to Sequencing.com's technology is via API. Because of this, you will be required to have some knowledge about making REST API requests and parsing the returned JSON data.

Once the data is available to your code then you may use it in your code logic. E.g. if you are creating a mobile app for the Apple iPhone then you might code your app in Objective-C or Swift and make API calls to the Sequencing.com backend.

If your app requires access to a user’s data then in your app you will be required to enable OAuth based authentication. If the user "Accepts" that your app and any app chains that your app may use may then access the user's genetic data stored at Sequencing.com. The user's genetic data will be made available only after you have passed the OAuth Token that was supplied.

You will then be able to use the returned data from the call in your code logic. At this point it will be up to you to use the data for your requirements. E.g. you might want to show tabular data, then you will be required to parse the data and make that as a data-source to the table controls in iOS.

Once your app has been created, you may upload it to iTunes Connect and if accepted by Apple then it would be available to end users.

Please note:

• Only the genetic data pertinent to your app or the app chains you are using will be accessed.
• While an App +RTP that are run on a platform outside of Sequencing.com may use an App Chain that utilizes, analyzes, processes, etc. a user's entire genome, Apps +RTP cannot retrieve or download a user's entire genome. 
• While Apps +RTP can access and use data from within a user's genetic data file, Apps +RTP cannot download any of the actual genetic data files.
• Apps +RTP are prohibited by Sequencing.com's Terms of Use from storing the output of an app chain. 
  • Updates to existing app chain may be released from time to time and seamlessly integrated into RTP. The benefit to you is that you do not have to recode your app each time an app chain is updated. This also means, however, that for users to always receive the most up-to-date (ie Real-Time) personalization, app chains must be re-run each time the app function is accessed that utilized +RTP technology. 
• Apps +RTP are also prohibited from storing a user's genetic data.
  • Sequencing.com provides secure, HIPAA compliant storage of genetic data. Our Terms of Use allow for genetic data to be accessed but not stored. This is a necessary feature to help protect the security and ensure integrity of our user's genetic data.

Call our APIs passing in the correct parameters and generate the data that you require.

For example, this is as simple as passing the AppID of a certain app and correct parameters for that API to execute. If the validation passes then the app will execute and a JobID will be returned to your app.

You may then call another API passing in the JobID and you will return the status of your job. Please note that you will be responsible for coding a timer function to poll the job status API.

Once the job has completed you may then call another API passing in the JobID and the generated data will be returned to your code. You may then use the data as you see fit.

The instructions below are for submitting an app chain to be made accessible through Sequencing.com's API. This means the app chain will be hosted on our platform and when an API call is made to the app chain, the chain will run using our computing resources. 

To submit an app chain, simply submit a Support Request and select I want to submit my app.

Please include the following details in your request:

1. Name of app
2. Coding language your app chain is written in
3. Are the API calls already coded?
   • If no, do you want assistance writing the API calls?
   • If yes, is the API call RESTful?
   • If yes, what language are the API calls written in?
4. What does your app chain do?
5. What is the output of your app chain (ie what is returned with the API response)? (JSON string, GFF3, PDF, SVG, CSV, genotypes, etc.)
6. Who will be the likely users of your app chain? (Individuals, Bioinformaticians, Researchers, Healthcare Professionals, etc?)

You do not need to submit actual code with this initial request. After submitting your request, a member of our App Chain Onboarding team will contact you to further discuss your app chain.

The Weather My Way +RTP app is an open source web-based weather app that uses Real-Time Personalization technology. We created this app so that you can experience an app that uses RTP while also having access to the app's source code.

The Weather My Way +RTP app combines weather forecast with an analysis of the app user's genes (using App Chains). The app then provides the user with daily, personalized recommendations that optimize the app user's wellness and longevity.

Even a weather app can now be personalized to the app-user in real-time!

Weather My Way +RTP                  GitHub repo

App Workflow:

• End user installs the app on their device or uses it via their computer.

• End user then enters their login details and internally an API key is passed to the app.

• The app can now access the end user’s data and the available data files are displayed to the user.

• The user can then select the data file upon which the app can be run.

• On the next screen the user can select their geographic location. At this point the app communicates with an external weather app and downloads that data in real-time.

• The app then combines the user’s risk of skin cancer and the weather data and displays the information as follows:

  • If Sunny and temp is over 70 degrees F then based on the person's Melanoma Risk the following could appear as an app notification via the app:

    • Lower Risk and Normal Risk of Melanoma = It's going to be a sunny day today! Sequencing.com analyzed your genes and wanted to remind you that even though you are not at an increased risk for skin cancer, you should either put on sunscreen today or avoid the sun because too much sun exposure can cause premature aging.

    • Slightly Increased Risk and Moderate Risk of Melanoma = It's going to be a sunny day today! Sequencing.com analyzed your genes and it's important that you apply a broad-spectrum sunscreen with a SPF of 30 or higher this morning to your face, neck, arms and any other exposed skin. You should also reapply the sunscreen again at around noon and we'll remind you at that time so you don't forget. If you'd like to know why this personalized recommendation is being made, please click here.

    • High Risk and Very High Risk of Melanoma = It's going to be a sunny day today! Sequencing.com analyzed your genes and it's extremely important that you apply a broad-spectrum sunscreen with a SPF of 30 or higher this morning to your face, neck, arms and any other exposed skin. You should also reapply the sunscreen again at around noon and we'll remind you at that time so you don't forget. If you'd like to know why this personalized recommendation is being made, please click here.

Thus we are able to combine real-time weather data with the genetic data and produce a personalized risk assessment report based on real-time weather data.