Your session has expired. Please click "Refresh" to refresh the page.
Nuclear Receptor Signaling Atlas
A research resource for the nuclear receptor signaling community
Newsletter Sign Up
Nursa Transcriptomine Datasets public REST API (v0.9) documentation.

Transcriptomine Datasets Query
  • API URL: or
  • Data access method: GET
  • Request parameters:
      The following are the Dataset Search parameters:
    • genes.symbol Valid values limited to HGNC gene symbols
    • genes.entrezgeneID Valid values limited to NCBI entrezGene ID
    • ligand.source and ligand.sourceID
  • One of the Dataset Identifier parameters genes.symbol or genes.entrezgeneID or ligand.source, is required
  • Valid values for ligand.sourceID parameter are : pubchem, chebi, cas, iuphar.
  • All data exchange is in JSON format.
  • You may also request the data in JSONP format. Use callback parameter, callback
  • Results are limited to a Maximum of 1000 dataset records for any one call.
  • To get response with a smaller size/compressed data, request a gzipped response. To do so, set your HTTP headers accordingly.

Get by Gene, HGNC symbol (eg symbol=AR): rest/transcriptomine/datasets?genes.symbol=AR
Get by Chemical, via CAS (eg id=446-72-0): rest/transcriptomine/datasets?ligand.source=446-72-0&ligand.sourceID=cas
  • Sample API Response Test (dummy data response)
  • Live API Test by Gene symbol AR
  • Live API Test by Gene Entrez GeneId 367
  • Live API Test for ligand 17β-estradiol, using cas id 50-28-2
  • Live API Test for Ligand 17β-estradiol, using pubchem id 5757
  • Live API Test for Ligand 17β-estradiol, using chebi id 16469
  • Live API Test for Ligand 17β-estradiol, using iuphar id 1012

  • Result: Array dataset objects
    							"releaseDate":"release date in format yyyy-MM-dd"
    HTTP System Response
    The REST Web services will return the following HTTP status response. The following HTTP stati are currently supported:
  • HTTP 200 OK. Even with no data ( e.g. Too Many results, unknown identifier), status 200 is returned.
  • HTTP 400 Bad Request. Client request does not conform to the REST URL requirements, e.g. Unknown parameter name received
  • HTTP 413. Based on client request, too many results would be returned. Client must modify the request to receive an appropriate number of results.
  • HTTP 500 Server Error: For all cases of Internal Server Error. Server unable to proceed. Rare indeed. Please let us know.
  • System Limitation
    Client applications should adhere to the following API restrictions, or future calls will be throttled.
  • Limit requests frequency to max of 3 requests per seconds.
  • If client receives a server error (HTTP 500), allow some time before making same call to the API.
  • Utilize local caching. Depending on your use case, local caching will prevent hitting API frequency limitations, for example, prevents each of your individual UI user's actions initiating an API request.
  • You may use ajax to call API. In the future we may limit this ability, so we'd have to register your domain to be allowed access.