Export Nightscout data and use read-only API access

Choose the data and date range

Nightscout can contain glucose entries, treatments (such as recorded meals and boluses), device status and profiles. Availability depends on what the uploader actually sent. A report or export does not establish that every source record was imported, and IOB may be recorded by a device or calculated separately.

For a report, open the Nightscout dashboard menu, Reports, and choose the date range and timezone. See report guidance.

For JSON exports, use Nightscout's API. The uploader's AAPS V1/V3 client choice does not by itself determine which read-only export API the hosted Nightscout server supports. Do not make the customer repeatedly supply uploader settings before explaining the export route.

Read-only API3 authentication

Create a dedicated subject with the readable role under Nightscout Admin Tools > Add New Subject. On supported current Nightscout deployments, an API3 client exchanges that access token by sending GET /api/v2/authorization/request/{accessToken} to the same complete site origin. A successful response supplies a temporary JWT. Send that JWT using the Authorization: Bearer header for API3 reads.

Never put a real token into support chat, a public script, logs, shared links or screenshots. A readable role is sufficient for read operations; do not recommend admin solely because a read-only exchange returned 403. The exact HTTP response, complete credential-free host, deployed Nightscout version and request path distinguish URL, proxy and authentication problems. A 401/403/404 is not proof that a customer must enable an undocumented portal setting. If the confirmed route still fails, contact support with the redacted response and client details.

API collections and complete exports

The API3 collections include /api/v3/entries, /api/v3/treatments, /api/v3/devicestatus and /api/v3/profile. Consult the Nightscout API3 specification for the collection's filters, sort fields, response envelope and pagination. A single default response is not a complete multi-month export. Request the intended range in pages or bounded date windows, preserve the original timestamps and check coverage.

Glucose comes from entries; recorded carbohydrates and boluses come from treatments. Device-reported IOB and related status depend on available device-status records and their source-specific fields. An empty result does not prove that the source never had records. Check date filters, timezone, permissions and whether those records exist in Nightscout.

Sharing a medical-data export with a third-party assistant is a separate decision. Export only the necessary range and fields, remove unrelated identifiers, and never share access credentials. Nightscout and external assistants do not replace advice from the person's healthcare team.