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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Truepill

Truepill Transfers API

Pharmacy-to-pharmacy prescription transfers.

Documentation Provider Profile APIs.io OpenAPI GitHub

Truepill Transfers API is one of 9 APIs that Truepill publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transfers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 22 operations across 18 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

Requests are made against a single base URL, https://rxapi.fuzehealth.com.

22 operations 18 paths 32 schemas 14 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://rxapi.fuzehealth.com/v1
Authentication
API Key
Contact
FuzeRx Support
Resource Areas
1

Authentication & Security 1

Truepill Transfers API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (apiKey). By default, every request must be authenticated.

  • apiKey — API key passed in the Authorization header. Separate keys are issued for sandbox and production.

Paths & Operations 22

Across 18 paths, the API surfaces 22 operations — 14 GET, 8 POST. Each is listed below with its method, path, parameters, and response codes.

transfers 22

Pharmacy-to-pharmacy prescription movement: transfer requests, direct transfers (v1/v2), external transfers, and external pharmacy location matching.

POST
/api/v1/direct_transfer
Create Direct Transfer
postApiV1Direct_transfer body → 202400404
GET
/api/v1/direct_transfer/{direct_transfer_token}
Get Direct Transfer by token
getApiV1Direct_transferDirect_transfer_token 1 param → 200403404
GET
/api/v1/external_location_matches
Search for specific external location using address information
getApiV1External_location_matches → default
POST
/api/v1/external_location_matches
Query external locations for multiple addresses, and will reply back with a map linking to the matched external location, or indication that one does not exist yet
postApiV1External_location_matches → default
GET
/api/v1/external_locations
Search for external locations using zip code
getApiV1External_locations → default
GET
/api/v1/external_locations/{id}
Get a specific external location by id
getApiV1External_locationsId → default
GET
/api/v1/external_transfers/{id}
Get external transfer details
getApiV1External_transfersId → default
GET
/api/v1/transfer_request
Get a list of Transfers
getApiV1Transfer_request → 200
POST
/api/v1/transfer_request
Create a Transfer
postApiV1Transfer_request body → 201400404
GET
/api/v1/transfer_request/{token}
Get a Transfer by token
getApiV1Transfer_requestToken 1 param → 200404
POST
/api/v2/direct_transfer
Create Direct Transfer v2
postApiV2Direct_transfer body → 200400404
POST
/v1/direct_transfer
Create Direct Transfer
postV1Direct_transfer body → 202400404
GET
/v1/direct_transfer/{direct_transfer_token}
Get Direct Transfer by token
getV1Direct_transferDirect_transfer_token 1 param → 200403404
GET
/v1/external_location_matches
Search for specific external location using address information
getV1External_location_matches → default
POST
/v1/external_location_matches
Query external locations for multiple addresses, and will reply back with a map linking to the matched external location, or indication that one does not exist yet
postV1External_location_matches → default
GET
/v1/external_locations
Search for external locations using zip code
getV1External_locations → default
GET
/v1/external_locations/{id}
Get a specific external location by id
getV1External_locationsId → default
GET
/v1/external_transfers/{id}
Get external transfer details
getV1External_transfersId → default
GET
/v1/transfer_request
Get a list of Transfers
getV1Transfer_request → 200
POST
/v1/transfer_request
Create a Transfer
postV1Transfer_request body → 201400404
GET
/v1/transfer_request/{token}
Get a Transfer by token
getV1Transfer_requestToken 1 param → 200404
POST
/v2/direct_transfer
Create Direct Transfer v2
postV2Direct_transfer body → 200400404

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are Model139 (19 properties), Model67 (14 properties), Model64 (11 properties), CreateDirectTransfer (7 properties). Each schema is shown below with its type and property counts.

Model181
object
3 properties
Model140
object
1 property
Model138
object
5 properties 5 required
Model177
object
6 properties
Model30
object
4 properties
Model65
object
5 properties
Model29
object
2 properties
Model49
object
3 properties
Model142
object
3 properties
TransferTo
object
Pharmacy to transfer prescriptions to
4 properties 2 required
transfer_medications
array
Model68
array
TransferFrom
object
Pharmacy to transfer prescriptions from
5 properties 4 required
Model175
object
3 properties
Model48
object
3 properties
Model67
object
14 properties
Model47
object
6 properties
Model176
array
CreateDirectTransfer
object
Create new direct transfer
7 properties 4 required
Model64
object
11 properties
icd_codes
object
Model66
array
Prescriber
object
Prescriber description
6 properties 4 required
Model139
object
Prescription description
19 properties 6 required
Model141
object
4 properties
Model24
object
3 properties
Model178
object
4 properties
Model180
array
Model31
array
Model179
object
2 properties
Model69
object
3 properties
Model143
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

truepill-transfers-api-openapi.yml Raw ↑

Other APIs Truepill publishes across the network.

Truepill Insurance API
AE Profile APIs.io
Truepill Patients API
AE Profile APIs.io
Truepill Prescriptions API
AE Profile APIs.io
Truepill Webhooks API
AE Profile APIs.io
Truepill Fulfillment API
AE Profile APIs.io
Truepill Consults API
AE Profile APIs.io
Truepill Diagnostics API
AE Profile APIs.io
Truepill Media API
AE Profile APIs.io
#Transfers
← Back to T APIs
API Details
ID
truepill:truepill-transfers-api
Base URL
https://rxapi.fuzehealth.com/v1
Docs
https://rxdocs.fuzehealth.com
Provider
Truepill
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=truepill-transfers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/truepill-transfers-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Truepill Transfers 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.