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 Price Preferences API

A price preference is used to specify whether tax-inclusiveness is enabled for a context, such as a region or currency code.These API routes allow admin users to manage whether a region or currency is tax inclusive.

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

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

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

Requests are made against 2 base URLs: http://localhost:9000, https://api.medusajs.com.

5 operations 2 paths 7 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.19.0
Base URL
https://{medusa-backend-domain}
Authentication
HTTP Basic, HTTP Bearer, API Key, HTTP Bearer
License
Resource Areas
1

Authentication & Security 4

Medusa Price Preferences API declares 4 security schemes for authenticating requests. It accepts HTTP basic authentication (api_token). It accepts HTTP bearer tokens (jwt_token). An API key is passed in the cookie as connect.sid (cookie_auth). It accepts HTTP bearer tokens (reset_password).

Paths & Operations 5

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

Price Preferences 5

A price preference is used to specify whether tax-inclusiveness is enabled for a context, such as a region or currency code. These API routes allow admin users to manage whether a…

GET
/admin/price-preferences
List Price Preferences
GetPricePreferences 11 params → 200400401404409422500
POST
/admin/price-preferences
Create Price Preference
PostPricePreferences 1 param body → 200400401404409422500
GET
/admin/price-preferences/{id}
Get a Price Preference
GetPricePreferencesId 2 params → 200400401404409422500
POST
/admin/price-preferences/{id}
Update a Price Preference
PostPricePreferencesId 2 params body → 200400401404409422500
DELETE
/admin/price-preferences/{id}
Delete a Price Preference
DeletePricePreferencesId 1 param → 200400401404409422500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are AdminPricePreference (7 properties), AdminPricePreferenceListResponse (5 properties), AdminCreatePricePreference (3 properties), AdminUpdatePricePreference (3 properties). Each schema is shown below with its type and property counts.

Error
object
3 properties
AdminPricePreferenceDeleteResponse
object
The details of the deleted price preference.
3 properties 3 required
AdminUpdatePricePreference
object
The details to update in the price preference.
3 properties
AdminPricePreferenceResponse
object
The price preference's details.
1 property 1 required
AdminPricePreferenceListResponse
object
The paginated list of price preferences.
5 properties 4 required
AdminPricePreference
object
The price preference's details.
7 properties 7 required
AdminCreatePricePreference
object
The price preference's details.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

medusa-price-preferences-api-openapi.yml Raw ↑

Other APIs Medusa publishes across the network.

Medusa GraphQL API
Medusa MCP Remote Server
Medusa Api Keys API
Medusa Auth API
Medusa [auth Provider] API
Medusa Campaigns API
Medusa Carts API
Medusa Claims API
Medusa Collections API
Medusa Currencies API
Medusa Customer Groups API
Medusa Customers API
Where this information came from

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