Prescrypto · Authentication Profile

Prescrypto Authentication

Authentication

Prescrypto secures its APIs with apiKey across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyHealthcareElectronic PrescriptionseRxPharmacyTelemedicineMedicalMexicoLATAM
Methods: apiKey Schemes: 2 OAuth flows: API key in: header

Security Schemes

TokenAuth apiKey
· in: header (Authorization)
JWTAuth apiKey
· in: header (Authorization)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: searched
source: openapi/prescrypto-openapi.yml
docs: https://www.prescrypto.com/docs
summary:
  types:
  - apiKey
  api_key_in:
  - header
  notes: >-
    Prescrypto uses HTTP Token auth for the core integration API (Authorization: Token <key>),
    issued through direct communication. Keys can be private (server-side) or public (browser).
    The standard-drug (products) endpoint uses a separate JWT token (Authorization: JWT <token>)
    on a distinct host (SD_ENDPOINT), provisioned by email. Pharmacy tokens are scoped to the
    pharmacy endpoints only.
schemes:
- name: TokenAuth
  type: apiKey
  in: header
  parameter: Authorization
  scheme_prefix: Token
  description: 'HTTP Token auth. Send: Authorization: Token <your-key>. Keys are issued by Prescrypto
    via direct communication and can be private (server-side) or public (browser).'
  sources:
  - openapi/prescrypto-openapi.yml
- name: JWTAuth
  type: apiKey
  in: header
  parameter: Authorization
  scheme_prefix: JWT
  description: 'JWT auth for the standard-drug (products) endpoint. Send: Authorization: JWT <token>.
    Endpoint host (SD_ENDPOINT) and token are provisioned by Prescrypto via email.'
  sources:
  - openapi/prescrypto-openapi.yml