Variable Name Converter API
Overview
To use Variable Name Converter, you need an API key. You can get one by creating a free account and visiting your dashboard.
POST Endpoint
https://api.apiverve.com/v1/variablenameconverterExample
How to call the Variable Name Converter API in different programming languages.
curl -X POST \
"https://api.apiverve.com/v1/variablenameconverter" \
-H "X-API-Key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"variables": [
"myVariableName",
"another_var_name",
"SomeClassName",
"kebab-case-name",
"CONSTANT_VALUE"
],
"to": "snake_case"
}'const response = await fetch('https://api.apiverve.com/v1/variablenameconverter', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
},
body: JSON.stringify({
"variables": [
"myVariableName",
"another_var_name",
"SomeClassName",
"kebab-case-name",
"CONSTANT_VALUE"
],
"to": "snake_case"
})
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
payload = {
"variables": [
"myVariableName",
"another_var_name",
"SomeClassName",
"kebab-case-name",
"CONSTANT_VALUE"
],
"to": "snake_case"
}
response = requests.post('https://api.apiverve.com/v1/variablenameconverter', headers=headers, json=payload)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
"bytes"
"encoding/json"
)
func main() {
payload := map[string]interface{}{
"variables": "myVariableName,another_var_name,SomeClassName,kebab-case-name,CONSTANT_VALUE",
"to": "snake_case"
}
jsonPayload, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/variablenameconverter", bytes.NewBuffer(jsonPayload))
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": {
"results": [
{
"original": "myVariableName",
"converted": "my_variable_name"
},
{
"original": "another_var_name",
"converted": "another_var_name"
},
{
"original": "SomeClassName",
"converted": "some_class_name"
},
{
"original": "kebab-case-name",
"converted": "kebab_case_name"
},
{
"original": "CONSTANT_VALUE",
"converted": "c_o_n_s_t_a_n_t__v_a_l_u_e"
}
],
"count": 5,
"targetFormat": "snake_case"
}
}Authentication
The Variable Name Converter 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 Variable Name Converter API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Variable Name Converter API:
Convert Variable Names
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
variables | array | required | Array of variable names to convert (max 100) | - | |
to | string | required | Target naming convention Supported values: camelCasePascalCasesnake_casekebab-caseCONSTANT_CASE | - |
Response
The Variable Name Converter 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>
<results>
<result>
<original>myVariableName</original>
<converted>my_variable_name</converted>
</result>
<result>
<original>another_var_name</original>
<converted>another_var_name</converted>
</result>
<result>
<original>SomeClassName</original>
<converted>some_class_name</converted>
</result>
<result>
<original>kebab-case-name</original>
<converted>kebab_case_name</converted>
</result>
<result>
<original>CONSTANT_VALUE</original>
<converted>c_o_n_s_t_a_n_t__v_a_l_u_e</converted>
</result>
</results>
<count>5</count>
<targetFormat>snake_case</targetFormat>
</data>
</response>
status: ok
error: null
data:
results:
- original: myVariableName
converted: my_variable_name
- original: another_var_name
converted: another_var_name
- original: SomeClassName
converted: some_class_name
- original: kebab-case-name
converted: kebab_case_name
- original: CONSTANT_VALUE
converted: c_o_n_s_t_a_n_t__v_a_l_u_e
count: 5
targetFormat: snake_case
| key | value |
|---|---|
| results | [{original:myVariableName,converted:my_variable_name},{original:another_var_name,converted:another_var_name},{original:SomeClassName,converted:some_class_name},{original:kebab-case-name,converted:kebab_case_name},{original:CONSTANT_VALUE,converted:c_o_n_s_t_a_n_t__v_a_l_u_e}] |
| count | 5 |
| targetFormat | snake_case |
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 |
|---|---|---|---|
| [ ] Array items: | array[5] | Array of converted variable names with original and converted values | |
â”” original | string | Original variable name before conversion | |
â”” converted | string | Variable name after conversion to target format | |
count | number | Number of variables converted in the request | |
targetFormat | string | Target naming convention used for conversion |
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 Variable Name Converter through GraphQL to combine it with other API calls in a single request. Query only the variable name converter 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 {
variablenameconverter(
input: {
variables: ["myVariableName","another_var_name","SomeClassName","kebab-case-name","CONSTANT_VALUE"]
to: "snake_case"
}
) {
results
count
targetFormat
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Variable Name Converter 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
Variable Name Converter 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 Variable Name Converter 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 Variable Name Converter
Official Variable Name Converter packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Variable Name Converter 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 Variable Name Converter?
How many credits does Variable Name Converter cost?
Each successful Variable Name Converter 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 variable name converter lookups.
Can I use Variable Name Converter in production?
The free plan is for testing and development only. For production use of Variable Name Converter, 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 Variable Name Converter from a browser?
What happens if I exceed my Variable Name Converter credit limit?
When you reach your monthly credit limit, Variable Name Converter 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.








