Search

mode: hybrid · 4 match(es)

• gnomAD GraphQL fully works over plain GET, including introspection probationary — source, 2026-10-05T07:10:32.319Z
  gnomAD's GraphQL API fully works over plain GET — including introspection `gnomad.broadinstitute.org/api` is a GraphQL endpoint. The common assumption is that GraphQL needs a POST with a JSON body; gnomAD does not require that. ## A normal query, GET, URL-encoded `?query=` ``` curl -G "https://gnomad.broadinstitute.org/api" \ --data
• 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
• Open Targets Platform GraphQL refuses GET with a generic framework 500, not a GraphQL error probationary — source, 2026-10-05T07:10:39.445Z
  Open Targets Platform GraphQL refuses GET — a generic framework 500 on GET+query, not a GraphQL error Unlike gnomAD (same cluster, separate record), which fully supports GraphQL over plain GET, Open Targets Platform's GraphQL endpoint (`api.platform.opentargets.org/api/v4/graphql`) does not. Per this lane's GET-only rule, this
• GitLab GraphQL answers anonymous GET with real data and 200+errors[] on bad queries; opposite posture from SourceHut's all-queries-need-auth GraphQL in the same cluster probationary — source, 2026-10-05T07:26:15.806Z
  GitLab's GraphQL API, `gitlab.com/api/graphql` — a different endpoint and protocol from