# MyOme

> MyOme is a CLIA-certified, CAP-accredited clinical laboratory in Menlo Park, California that
> sequences a patient's whole genome once and re-interprets it over time. It publishes a partner-facing
> REST API for ordering sequencing and analysis, tracking laboratory orders, and retrieving results.

Generated by API Evangelist from MyOme's published OpenAPI document and public website on 2026-08-26.
MyOme does not publish an llms.txt of its own (https://myome.com/llms.txt returned 404).

## API

- [MyOme API reference (RapiDoc)](https://api.myome.com/0/ui/): The published API reference. OpenAPI 3.0.2, info.version 2.51.0.
- [OpenAPI document](https://api.myome.com/0/openapi.json): 63 paths; operation detail is published for 8 of them to anonymous callers.
- Production base URL: https://api.myome.com/0/
- External sandbox base URL: https://api.sbx.myome.com/0/ (same document, for partner testing/development)

### What the API does

- List the sequencing and analysis **Products** available to the client (product ids are prefixed `PR`).
- Submit a **Requisition** for a sample (prefixed `RQ`). One **Order** (prefixed `OR`) is created per Product requested.
- Check requisition and order status through SUBMITTED -> AWAITING_SAMPLE -> ANALYZING -> CLINICIAN_REVIEW -> COMPLETED (also APPROVED, DENIED, CANCELED, FAILED, REFERRAL_LAB_LD_REVIEW).
- Retrieve **Reports** — sequencing data, structured interpretation data, and PDF reports.

### Publicly documented operations

- `GET /product` — list orderable products.
- `GET /consent` — list consent types; requires a `consents` query parameter.
- `GET /requisition` — list the caller's open requisitions (paginated with `page`/`per_page`, sortable).
- `POST /requisition` — create a requisition. Creates billable laboratory orders.
- `GET /requisition/{requisition_id}` — fetch one requisition.
- `GET /order/{order_id}` — order status and, when complete, result access.
- `POST /institutional/partner-requisition` — create a partner-scoped institutional requisition.
- `POST /institutional/campaign/{campaign_code}/individual` — enrol an individual into an institutional campaign.

### Authentication

Bearer JWT: `Authorization: Bearer <token>`. Tokens are issued by MyOme's Keycloak at auth.myome.com
using partner-specific credentials that MyOme sends by secure email at account creation. Tokens
refresh hourly. There is no self-service sign-up for API access.

### What an agent must know before calling

- **Writes are irreversible through the API.** `POST /requisition` orders a clinical genomic test
  against a patient sample. No cancel, void or refund operation is published, and no reversal window
  is stated anywhere. Escalate to support@myome.com rather than attempting a reversal.
- **There is no idempotency key.** A retried POST is a second billable test. Do not auto-retry writes.
- **There are no published rate limits** and no RateLimit/Retry-After headers, so there is no back-off signal.
- **Everything here is PHI.** Requests and responses carry identified patient names, dates of birth,
  addresses, contact details, family history and genomic findings under HIPAA.
- **The runtime error envelope is RFC 9457** (`application/problem+json` with type/title/detail/status),
  which differs from the `application/json` StructuredError envelope the spec declares.

## Products and tests

- [Our tests](https://myome.com/our-tests)
- [Proactive Health](https://myome.com/our-tests/proactive-health): Single-Gene Risk, Medication Response (pharmacogenomics), Integrated Polygenic Risk Score (iPRS).
- [Diagnostic](https://myome.com/our-tests/diagnostic): Rare Disease Genome, Rare Disease Exome, Rare Disease Copy Number Analysis.
- [Our approach](https://myome.com/our-approach)

## Who MyOme serves

- [Patients](https://myome.com/who-we-serve/patients) — patient portal at https://patients.myome.com/
- [Providers](https://myome.com/who-we-serve/providers) — provider portal at https://providers.myome.com/
- [Employers](https://myome.com/who-we-serve/employers)
- [Healthcare systems](https://myome.com/who-we-serve/healthcare-systems)

## Company and policy

- [About MyOme](https://myome.com/about-us)
- [News](https://myome.com/about-us/news)
- [Careers](https://myome.com/about-us/careers)
- [Privacy and security](https://myome.com/about-us/privacy-and-security) — CLIA certified, CAP accredited, HIPAA compliant
- [Contact](https://myome.com/contact-us) — support@myome.com
- [FAQ](https://myome.com/resources/faq)
- [Resource library](https://myome.com/resources/resource-library)
- [MyOme Access financial assistance](https://myome.com/access)
- [GitHub organization](https://github.com/myome) — genomics research tooling; no API client libraries

## Legal

- [Terms of service](https://myome.com/legal/terms-of-service)
- [Privacy notice](https://myome.com/legal/privacy-notice)
- [Privacy policy](https://myome.com/legal/privacy-policy)
- [HIPAA notice of privacy practices](https://myome.com/legal/hipaa-notice-of-privacy-practices)

## Not published

MyOme publishes no SDK in any package registry, no CLI, no MCP server, no A2A agent card, no
GraphQL endpoint, no AsyncAPI or webhook surface, no status page, no API changelog, no pricing page,
no rate limits, no /.well-known/ document of any kind, and no bug-bounty or vulnerability-disclosure
policy. Each of those was probed on 2026-08-26 and recorded as an absence, not assumed.