Cost of Living API
Overview
To use Cost of Living, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/costlivingExample
How to call the Cost of Living API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/costliving?location=California" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/costliving?location=California', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/costliving?location=California', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/costliving?location=California", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"from": {
"searchedLocation": "California",
"region": "west-large",
"regionName": "West Large Metros (LA, SF, Seattle, Phoenix, Denver area)",
"costIndex": 118
},
"to": {
"searchedLocation": "Texas",
"region": "south-large",
"regionName": "South Large Metros (Dallas, Houston, Atlanta, Miami, DC area)",
"costIndex": 103
},
"comparison": {
"costDifference": -12.7,
"direction": "less expensive",
"salaryEquivalent": {
"description": "A $100,000 salary in California is equivalent to $87,288 in Texas",
"fromSalary": 100000,
"equivalentSalary": 87288
}
}
}
}Authentication
The Cost of Living API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Cost of Living API directly in your browser with live requests and responses.
Parameters
The Cost of Living API supports multiple query options. Use one of the following:
Option 1: Get Cost of Living
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
location | string | optional | State name, state code (e.g., CA, NY), or major city name. Omit for all regions ranked. | - |
Option 2: Compare Cost of Living
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
from | string | required | Origin location (state name, code, or major city) | - | |
to | string | required | Destination location to compare against | - | |
salaryPremium | number | optional | Current salary to calculate equivalent in destination | - |
Response
The Cost of Living API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<from>
<searchedLocation>California</searchedLocation>
<region>west-large</region>
<regionName>West Large Metros (LA, SF, Seattle, Phoenix, Denver area)</regionName>
<costIndex>118</costIndex>
</from>
<to>
<searchedLocation>Texas</searchedLocation>
<region>south-large</region>
<regionName>South Large Metros (Dallas, Houston, Atlanta, Miami, DC area)</regionName>
<costIndex>103</costIndex>
</to>
<comparison>
<costDifference>-12.7</costDifference>
<direction>less expensive</direction>
<salaryEquivalent>
<description>A $100,000 salary in California is equivalent to $87,288 in Texas</description>
<fromSalary>100000</fromSalary>
<equivalentSalary>87288</equivalentSalary>
</salaryEquivalent>
</comparison>
</data>
</response>
status: ok
error: null
data:
from:
searchedLocation: California
region: west-large
regionName: West Large Metros (LA, SF, Seattle, Phoenix, Denver area)
costIndex: 118
to:
searchedLocation: Texas
region: south-large
regionName: South Large Metros (Dallas, Houston, Atlanta, Miami, DC area)
costIndex: 103
comparison:
costDifference: -12.7
direction: less expensive
salaryEquivalent:
description: A $100,000 salary in California is equivalent to $87,288 in Texas
fromSalary: 100000
equivalentSalary: 87288
| key | value |
|---|---|
| from | {searchedLocation:California,region:west-large,regionName:West Large Metros (LA, SF, Seattle, Phoenix, Denver area),costIndex:118} |
| to | {searchedLocation:Texas,region:south-large,regionName:South Large Metros (Dallas, Houston, Atlanta, Miami, DC area),costIndex:103} |
| comparison | {costDifference:-12.7,direction:less expensive,salaryEquivalent:{description:A $100,000 salary in California is equivalent to $87,288 in Texas,fromSalary:100000,equivalentSalary:87288}} |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
from | object | - | |
â”” searchedLocation | string | The origin location name or code provided | |
â”” regionPremium | string | Region identifier for origin location | |
â”” regionNamePremium | string | Full region name with major cities for origin | |
â”” costIndex | number | Cost of living index for origin location | |
to | object | - | |
â”” searchedLocation | string | The destination location name or code provided | |
â”” regionPremium | string | Region identifier for destination location | |
â”” regionNamePremium | string | Full region name with major cities for destination | |
â”” costIndex | number | Cost of living index for destination location | |
comparison | object | - | |
â”” costDifference | number | Percentage difference in cost between locations | |
â”” direction | string | Whether destination is more or less expensive | |
â”” salaryEquivalent | object | - | |
â”” descriptionPremium | string | Human-readable salary equivalency explanation | |
â”” fromSalaryPremium | number | Starting salary amount in origin location | |
â”” equivalentSalaryPremium | number | Equivalent salary needed in destination location |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Cost of Living through GraphQL to combine it with other API calls in a single request. Query only the cost of living data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
costliving(
input: {
location: "California"
}
) {
from {
searchedLocation
region
regionName
costIndex
}
to {
searchedLocation
region
regionName
costIndex
}
comparison {
costDifference
direction
salaryEquivalent {
description
fromSalary
equivalentSalary
}
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Cost of Living API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Cost of Living requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Cost of Living API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Cost of Living
Official Cost of Living packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Cost of Living works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Cost of Living?
How many credits does Cost of Living cost?
Each successful Cost of Living API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful cost of living lookups.
Can I use Cost of Living in production?
The free plan is for testing and development only. For production use of Cost of Living, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Cost of Living from a browser?
What happens if I exceed my Cost of Living credit limit?
When you reach your monthly credit limit, Cost of Living API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








