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 Translations API

A translation is a localized version of content in a specific locale. For example, a product description in French.These API routes allow admin users to manage translations for different locales and resources.

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

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

This API exposes 6 operations across 6 paths, and defines 13 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.

6 operations 6 paths 13 schemas 4 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 Translations 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 6

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

Translations 6

A translation is a localized version of content in a specific locale. For example, a product description in French. These API routes allow admin users to manage translations for d…

GET
/admin/translations
List Translations
GetTranslations 11 params → 200400401404409422500
POST
/admin/translations/batch
Manage Translations
PostTranslationsBatch body → 200400401404409422500
GET
/admin/translations/entities
List Translatable Entities
GetTranslationsEntities 7 params → 200400401404409422500
GET
/admin/translations/settings
List Translation Settings
GetTranslationsSettings 2 params → 200400401404409422500
POST
/admin/translations/settings/batch
Manage Translation Settings
PostTranslationsSettingsBatch body → 200400401404409422500
GET
/admin/translations/statistics
Retrieve Translation Statistics
GetTranslationsStatistics 2 params → 200400401404409422500

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are AdminTranslation (8 properties), AdminTranslationSettings (7 properties), AdminUpdateTranslation (5 properties), AdminTranslationEntitiesResponse (4 properties). Each schema is shown below with its type and property counts.

AdminTranslationSettingsResponse
object
The translation settings' details.
1 property 1 required
AdminUpdateTranslationSettings
object
The translation settings to update.
4 properties 1 required
Error
object
3 properties
AdminTranslationStatisticsResponse
object
The translation statistics details.
1 property 1 required
AdminCreateTranslation
object
The translation's details.
4 properties 4 required
AdminTranslationsBatchResponse
object
The batch response for managing translations.
3 properties 3 required
AdminTranslationEntitiesResponse
object
The list of translatable entities.
4 properties 4 required
AdminBatchTranslationSettings
object
The translation settings to create, update, or delete in batch.
3 properties
AdminBatchTranslationSettingsResponse
object
The result of managing the translation settings in batch.
3 properties 3 required
AdminUpdateTranslation
object
The data for updating a translation.
5 properties 1 required
AdminTranslation
object
The translation's details.
8 properties 8 required
AdminTranslationSettings
object
The translation settings details.
7 properties 7 required
AdminCreateTranslationSettings
object
The translation settings to create.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

medusa-translations-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 Translations 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.