---
title: "Health profile"
description: "Manage consent, saved conditions, and medications for the API key owner."
canonical_url: "https://scholarxiv.com/developers/docs/health-api/profile"
markdown_url: "https://scholarxiv.com/developers/docs/health-api/profile.md"
---

> For the complete documentation index, see [llms.txt](/llms.txt).

# Health profile
URL: /developers/docs/health-api/profile
LLM index: /llms.txt
Description: Manage consent, saved conditions, and medications for the API key owner.
Related: health-api, health-api/quickstart

# Health profile

The assistant reads the caller's health profile on every turn, the same way `/health` does.

```bash
curl https://scholarxiv.com/api/v1/health/profile \
  -H "Authorization: Bearer sxv_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"consentGiven":true,"conditions":["Type 2 diabetes"],"medications":["metformin"]}'
```

`consentGiven: true` is required. `GET /api/v1/health/profile` reads it. `DELETE /api/v1/health/profile?confirm=delete` removes the profile, trackers, and lab panels.

Profile writes replace the editable profile fields, rather than patching individual fields. To update medications or conditions, read the profile and submit the complete desired profile with consent. The profile stores arrays of medication and condition names; medication reference lookups do not alter those arrays.

Private data belongs to the API key owner and is shared with that account’s website and MCP workspace. Keys do not create separate patient accounts. Each user of an integration needs their own account and key.

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.
Docs-scoped sitemap: [/docs/sitemap.md](/docs/sitemap.md).
Well-known sitemap: [/.well-known/sitemap.md](/.well-known/sitemap.md).