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

MedTrainer Positions API

Public position lookup endpoints

MedTrainer Positions API is one of 6 APIs that MedTrainer publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, /.

2 operations 2 paths 7 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.medtrainer.com
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

MedTrainer Positions API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (ApiKeyHeader). It accepts HTTP bearer tokens (API key) (BearerAuth).

  • ApiKeyHeader — Preferred authentication header for protected endpoints.
  • BearerAuth — Alternative authentication scheme using Authorization: Bearer .

Paths & Operations 2

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

Positions 2

Public position lookup endpoints

GET
/api/v1/position
Search positions
searchPositions 3 params → 200401422429500
GET
/api/v1/position/{publicId}
Get a position by public ID
getPosition 1 param → 200401404429500502

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are PositionSearchBundle (5 properties), OperationOutcomeIssue (4 properties), Position (4 properties), OperationOutcomeDetails (2 properties). Each schema is shown below with its type and property counts.

Position
object
4 properties 1 required
PositionSearchEntry
object
1 property 1 required
OperationOutcomeIssue
object
4 properties 3 required
PositionSearchBundle
object
5 properties 5 required
OperationOutcome
object
2 properties 2 required
BundleLink
object
2 properties 2 required
OperationOutcomeDetails
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

medtrainer-positions-api-openapi.yml Raw ↑

Other APIs MedTrainer publishes across the network.

MedTrainer Departments API
MedTrainer Divisions API
MedTrainer Locations API
MedTrainer Practitioner Categories API
MedTrainer Practitioners API
Where this information came from

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