How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Huma Pfizer Hemophilia API

The Pfizer Hemophilia API from Huma — 1 operation(s) for pfizer hemophilia.

Huma Pfizer Hemophilia API is one of 77 APIs that Huma publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Pfizer Hemophilia. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a getting-started guide, and authentication docs.

This API exposes 2 operations across 1 path, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://workspace-gcp-uk.api.huma.com/api/integration/v1.

2 operations 1 paths 5 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://workspace-gcp-uk.api.huma.com/api/integration/v1
Authentication
API Key, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 3

Huma Pfizer Hemophilia API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (Hawk_Auth). It accepts HTTP bearer tokens (JWT) (JWT_Auth). It accepts HTTP bearer tokens (JWT) (jwtAuth).

  • Hawk_Auth — Hawk MAC authentication. Paste a full Authorization header value. Example: Authorization: Hawk id="userId:clientId", ts=" ", nonce=" ", mac=" "[, hash=" "][, e…
  • JWT_Auth — Use HTTP Bearer auth with a JWT. Send the token in the Authorization header: Authorization: Bearer The token should contain standard claims plus projectId and…

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Pfizer Hemophilia 2
GET
/api/hemophilia/v1/user/{user_id}/prerequisites
Retrieve Prerequisites
api_hemophilia_v1_user_prerequisites_retrieve_[retrieve_prerequisites] 1 param → 200
POST
/api/hemophilia/v1/user/{user_id}/prerequisites
Submit Prerequisites
api_hemophilia_v1_user_prerequisites_create_[submit_prerequisites] 1 param body → 201

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are QuestionnaireAnswerDRF (22 properties), HemophiliaPrerequisitesRequestObjectDRF (8 properties), HemophiliaPrerequisitesResponseObjectDRF (8 properties), QuestionnaireAnswerMediaFileDRF (3 properties). Each schema is shown below with its type and property counts.

ResultIdResponseObjectDRF
object
1 property
HemophiliaPrerequisitesResponseObjectDRF
object
8 properties 2 required
QuestionnaireAnswerDRF
object
22 properties 1 required
QuestionnaireAnswerMediaFileDRF
object
3 properties 2 required
HemophiliaPrerequisitesRequestObjectDRF
object
8 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

huma-pfizer-hemophilia-api-openapi.yml Raw ↑

Other APIs Huma publishes across the network.

Huma Mobile & Web SDK
Huma AI Engine API
Huma Appointment API
Huma Assets API
Huma Audit Log API
Huma Auth API
Huma Authorization Admin API
Huma Autocomplete API
Huma Billing API
Huma Billing Portal Route API
Huma Builder API
Huma Calendar Route API
Where this information came from

This is an independent, third-party profile of Huma Pfizer Hemophilia API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.