AUSTRALIAN ADHD PRESCRIBINGPUBLIC INFORMATION. ORIGINAL SOURCES.
FOR DEVELOPERS

Use the data.
Keep the context.

Free access with attribution

You may reuse our published summaries without an access fee, with a visible link to ADHD Rules and the original sources. Preserve the review status and dates. This permission covers our summaries, not third-party source material.

For a verified record: “Rules data: adhdrules.com.au, verified [record date]”. For an unverified state: “Rules data: adhdrules.com.au — under verification”. Never replace a verification date with the date you fetched the API.

Endpoints

  • GET /api/v2/rules — all eight states, consumer fields, current and upcoming.
  • GET /api/v2/rules/NSW — one state, with the same fields.
  • GET /api/v1/rules — original publication snapshot. Version 1 is preserved for existing clients; use version 2 for review freshness and age fields.

Read status before the answer

{
  "schema_version": "2.0",
  "states": [
    {
      "jurisdiction_code": "TAS",
      "status": "under_verification",
      "reason": "No human-reviewed rule has been published.",
      "verified_at": null,
      "current": null,
      "min_age_diagnose_gp": null,
      "min_age_continue_gp": null,
      "prescriber_terms": [],
      "official_list_url": null,
      "valid_until": null,
      "upcoming": null
    }
  ]
}

This abbreviated example shows one state. The complete response includes all eight and a generated_at timestamp. That timestamp means response creation, not human verification.

A null age means unknown, not that a GP pathway does not exist. Prescribing here means continuation of an existing treatment plan, not starting every medicine. Upcoming changes need a human-reviewed primary source; they never become current automatically. Unpublished research is excluded.

Freshness and traffic

Version 2 withholds current rules when the rule, consumer review or source checks are more than 45 days old. The valid_until field is the earliest expiry of the rule review, consumer-field review and source checks. Responses are cached for up to one hour; clients must still honour valid_until. Cache your requests and retry failures with backoff. No dedicated numeric API quota is configured; hosting protections still apply. Availability is not guaranteed.

Changes

Read the change history or subscribe to the RSS feed. RSS requires no personal information.