Shoe Size Converter is a tool for converting shoe sizes between US, UK, EU, CM, JP, AU, MX, and KR standards. It supports men, women, unisex, and child sizes.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Shoe Size Converter response payload
}
}
About the Shoe Size Converter API
Shoe Size Converter works by converting the input size to centimeters as a base measurement, then calculating equivalent sizes in all supported regions. Returns conversions for all international standards simultaneously.
What people use it for
- E-commerce
- Help international customers find their correct shoe size when shopping from different countries
- Travel Planning
- Convert shoe sizes when shopping abroad or purchasing from international retailers
- Size Charts
- Generate comprehensive size charts for footwear products with multiple regional standards
- Retail Apps
- Integrate size conversion features into shopping apps to improve customer experience
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Shoe Size Converter
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Shoe Size Converter API do?
How do I authenticate Shoe Size Converter API requests?
How much does the Shoe Size Converter API cost?
How fast is the Shoe Size Converter API?
What response formats does the Shoe Size Converter API support?
What HTTP method does the Shoe Size Converter API use?
Request parameters — GET /v1/shoesizeconverter
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
sizeRequired | string | 9 | The shoe size to convert |
fromRequired | string | us | Source regionusukeucmjpaumxkr |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
genderOptional | string | men | Gender sizingmenwomenunisexchilddefault unisex |
curl "https://api.apiverve.com/v1/shoesizeconverter?size=9&from=us&gender=men" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/shoesizeconverter
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"input_size": 9,
"input_region": "US",
"gender": "men",
"conversions": {
"cm": 29.1,
"jp": 29.1,
"us": 9,
"uk": 8.1,
"au": 8.1,
"eu": 43.7,
"mx": 13.7,
"kr": 43.7
},
"note": "Sizes are approximate and may vary by manufacturer"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
input_size | number | 9 | The size that was supplied |
input_region | string | "US" | Sizing system the input was given in |
gender | string | "men" | Gender sizing used for conversion |
conversions | object | {...} | The equivalent size in every supported sizing system |
cmPremium | number | 29.1 | Size in centimeters |
jpPremium | number | 29.1 | Japanese shoe size |
us | number | 9 | US shoe size |
uk | number | 8.1 | UK shoe size |
au | number | 8.1 | Equivalent Australian size |
euPremium | number | 43.7 | EU shoe size |
mx | number | 13.7 | Equivalent Mexican size |
kr | number | 43.7 | Equivalent Korean size, in millimetres |
note | string | "Sizes are approximate and may vary by manufacturer" | Caveat that sizes are approximate and vary by manufacturer |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Shoe Size Converter calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/shoesizeconverter
No SDK to install — this is a plain HTTPS call to /v1/shoesizeconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/shoesizeconverter" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/shoesizeconverter
Install the Node.js SDK, then call the Shoe Size Converter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/shoesizeconverterconst res = await fetch("https://api.apiverve.com/v1/shoesizeconverter", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/shoesizeconverter
No SDK to install — this is a plain HTTPS call to /v1/shoesizeconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/shoesizeconverter",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/shoesizeconverter
Install the C# / .NET SDK, then call the Shoe Size Converter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.ShoeSizeConverterusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/shoesizeconverter");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/shoesizeconverter
No SDK to install — this is a plain HTTPS call to /v1/shoesizeconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/shoesizeconverter", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/shoesizeconverter
No SDK to install — this is a plain HTTPS call to /v1/shoesizeconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/shoesizeconverter");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/shoesizeconverter
No SDK to install — this is a plain HTTPS call to /v1/shoesizeconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/shoesizeconverter")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Shoe Size Converter form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Shoe Size Converter API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Shoe Size Converter API.
Reference Data
- Birthstones
- CAA Record Parser
- Color Brightness Calculator
- Color Name Finder
- HTTP Status Code Lookup
- Mayan Calendar
- MIME Type Lookup
- Port Number Lookup
- Ring Size Converter
- Shoe Size Converter
- SRV Record Parser
Related articles
All articles →
API Rate Limiting Done Right: A Complete GuideLearn how to design rate limits that protect your API while maintaining good developer experience.Read 
Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read 
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read