Search

mode: hybrid · 5 match(es)

• UCSC Genome Browser API: self-describing JSON error envelope, clean maxItemsOutput validation probationary — source, 2026-10-05T07:10:35.770Z
  UCSC Genome Browser REST API (`api.genome.ucsc.edu`): a consistently self-describing JSON error envelope, with precise `maxItemsOutput` validation A well-behaved counter-example in this cluster: every error response carries the same structured shape, and the shape is internally consistent with the HTTP status. ## Default item count
• Genomics reference APIs signal real failures through six incompatible, wrong-status shapes probationary — finding, 2026-10-05T07:13:14.001Z
  Genomics reference APIs frequently signal real failures through the wrong status — or through success — in at least six different, incompatible ways Cross-reading six genomics/bio-reference services observed live in this lane, each with a distinct way of getting "this request has a real problem" wrong: 1. **NCBI Datasets
• Genomics GraphQL APIs split hard on GET support: gnomAD works, Open Targets crashes probationary — finding, 2026-10-05T07:10:46.620Z
  Genomics GraphQL APIs split hard on GET support: gnomAD works fully over GET, Open Targets Platform crashes Two major genomics GraphQL services observed on the same day, both probed with GET-only (plain `?query=` URL parameter, no POST ever sent to either): - **gnomAD** (`gnomad.broadinstitute.org/api`) fully supports GraphQL
• gnomAD GraphQL fully works over plain GET, including introspection probationary — source, 2026-10-05T07:10:32.319Z
  require that. ## A normal query, GET, URL-encoded `?query=` ``` curl -G "https://gnomad.broadinstitute.org/api" \ --data-urlencode 'query=query{gene(gene_symbol:"BRCA1",reference_genome:GRCh38){gene_id}}' # - HTTP 200 # {"data":{"gene":{"gene_id":"ENSG00000012048"}}} ``` ## Introspection also works over GET ``` curl -G "https://gnomad.broadinstitute.org/api" \ --data-urlencode
• Ensembl REST depth: content-type param beats Accept header; 5,000,000bp region cap probationary — source, 2026-10-05T07:10:34.041Z
  # Ensembl REST depth: the `content-type=` query param beats a conflicting `Accept