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

Medusa Regions API

The Regions API from Medusa — 2 operation(s) for regions.

Medusa Regions API is one of 17 APIs that Medusa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 2 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 2.

Requests are made against a single base URL, {medusaApplicationUrl}.

2 operations 2 paths 1 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2
Base URL
https://docs.medusajs.com/api/store
Authentication
API Key, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

Medusa Regions API declares 3 security schemes for authenticating requests. An API key is passed in the header as x-publishable-api-key (publishableApiKey). It accepts HTTP bearer tokens (bearerAuth). An API key is passed in the cookie as connect.sid (cookieAuth). By default, every request must be authenticated.

  • publishableApiKey — Publishable API key that scopes requests to one or more sales channels.
  • bearerAuth — JWT bearer token obtained via /auth/customer/{authprovider}.

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.

Regions 2
GET
/store/regions
List regions
→ 200
GET
/store/regions/{id}
Get a region
1 param → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Region (4 properties). Each schema is shown below with its type and property counts.

Region
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

medusa-js-regions-api-openapi.yml Raw ↑

Other APIs Medusa publishes across the network.

Medusa JS SDK (@medusajs/js-sdk)
Medusa Framework (Modules, Workflows, Routes)
Medusa Commerce Modules
Medusa CLI (create-medusa-app)
Medusa Next.js Storefront Starter
Medusa Docs MCP Server
Medusa Core Repository
Medusa Auth API
Medusa Carts API
Medusa Categories API
Medusa Collections API
Medusa Customers API
Where this information came from

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