Error
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 public REST API (v1.0) documentation.

Transcriptomine Datapoints Query
You need to apply for and get an API Key to make use of these APIs.
  • Contact NURSA support for an apiKey.
An API key is required to access the NURSA API, and must be included with every request. See later for restrictions.
  • All data exchange is in JSON format.
  • You may also request the data in JSONP format.
  • The maximum number of datapoints returned is 2000. If you would like to see more data returned, please contact NURSA support.
  • To get response with a smaller size/compressed data, request a gzipped response.

For example, to search for datapoints results for AR:
https://nursa.org/nursa/rest/api/1/datapoints/query/?apiKey=YOUR_API_KEY&geneSearchType=gene&gene=AR
API URL to get Datapoints search results
ResponseList of Nursa Transcriptomine Datapoints
Call URL https://nursa.org/nursa/rest/api/1/datapoints/query/
MethodGET
GET Paremeters Below are the query parameter to search on: All missing query parameters are treated as the specified default.
  • apiKey: REQUIRED apiKey to call API
  • callback: Optional jsonp callback method
  • geneSearchType: Either of "any","gene", "goTerm", or "disease"
    • If geneSearchType=gene, use gene parameter to provide NCBI HUGO gene symbol (any species)
    • If geneSearchType=goTerm, use goTerm parameter to provide Go Term name
    • If geneSearchType=disease, use disease parameter to provide OMIM disease name
  • gene: provide HUGO symbol. For multiple symbols, semicolon (;) separated list of symbols.
  • goTerm: provide a GoTerm. For multiple terms, semicolon (;) separated list of terms.
  • disease: provide an Omim disease Term. For multiple terms, semicolon (;) separated list of terms.
  • molecule:For nuclear receptors and coregulators, provide the NCBI Entrez gene symbol (any species). For Ligands, see ligandIdType below.
  • ligandIdType: Optional, but if present, one of CAS, PubChem, Chebi, IUPHAR. If present, provide the relevant molecule identifier that conforms to this Id scheme.
  • moleculeTreatmentTime: If a ligand is the regulatory molecule, you may include the duration of treatment for that regulatory molecule. If none provided, default of "any" applies.
      Valid TreatmentTime values are:
    • any (i.e. any time)
    • 1 (i.e. 1 hour or less )
    • 1-4 (i.e. greater than 1h, less or equal to 4h)
    • 4-24 (i.e. greater than 4 h, less or equal to 24h)
    • 24 (i.e. greater than 24h)
  • species: Default "all". Provide either Human, House Mouse, or Rat. If no species is selected, default "all" applies.
  • tissue: Provide the tissue or cell line string, e.g. Mammary gland, mammary carcinoma cells, MCF-7
  • significance: Default "0.05". Provide a numeric value. If none provided, default of less than 0.05 applies.
  • foldChange: Default 2. Provide a numeric value. If none provided, default of less than or equal to 2.0 applies.
  • direction: Default "any". Valid options: either, up, or down. If none provided, default of "any" applies.
  • count: Optional. Maximum number of datapoints to return for the query. Default is 5000.
  • findCount: Optional. To return just a count of query results without the result list. Set getCount=1 to activate.
  • Return Object List of Datapoints (See sample below)
    Sample Query Query for gene=AR and foldChange=5.0
    List of Datapoints.
    Sample List of Datapoint response
    [ { "id": "579932309", "symbol": "GREB1", "prob": "205862_at", "foldChange": 21.5053490468, "tissueName": "Female reproductive, mammary gland, epithelium, MCF-7 cells", "speciesCommonName": "Human", "experimentName": "17βE2 vs Veh | 100 nM, 12 h", "symbolSynonym": "GREB1", "probType": "AD9", "tissueCategory": "/Female reproductive/Mammary gland", "symbolUrl": "molecules/protein.jsf?doi=10.1621/KV4821QO65", "experimentNumber": "3", "datasetDoi": "10.1621/endTZMGb6Z", "pValue": 0, "regulatoryMoleculeSymbol": "17βE2", "regulatoryMoleculeName": "17β-estradiol", "moleculePathway": "ERs & Estrogens", "moleculePathwayArray": [ "ERs & Estrogens" ], "tissueCategoryArray": [ "/Female reproductive/Mammary gland" ] }, ... ]
    HTTP Status Response
    The following HTTP status codes are currently supported:
  • HTTP 200 : OK. Even with application errors( e.g. Too Many results, unknown identifier, see below), OK is returned
  • HTTP 400 : Bad Request. For cases where client request does not conform to the REST URL requirements, e.g. Request wasn't formatted correctly
  • HTTP 401 : Unauthorized. You need an apiKey to access the system
  • HTTP 406. The parameter provided (gene, disease, etc) does not translate to a known identifier within the system. Most likely cause is that the paramter value is incorrect or it is not being tracked by NURSA.
  • HTTP 413. Based on client request, too many results would be returned. The max allowed is 2000. Modify request to receive an appropriate number of results.
  • HTTP 429 : Exceeded allowed limits. Please follow api call limits.
  • HTTP 500 Server Error: For all cases of Internal Server Error. Server unable to proceed.
  • Application Error Message.
    Sample Application Error response
    {"status":406,"message":"No relevant identifier found for provided search parameter: ARARO"}
    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 your 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.
  • Transcriptomine Datasets Query