Variable Name Converter API
Variable Name Converter transforms variable names between different naming conventions including camelCase, snake_case, PascalCase, and kebab-case.
The Variable Name Converter API provides reliable and fast access to variable name converter data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
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/variablenameconverterCode Examples
Here are examples of 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)const https = require('https');
const url = require('url');
const options = {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
};
const postData = JSON.stringify({
"variables": [
"myVariableName",
"another_var_name",
"SomeClassName",
"kebab-case-name",
"CONSTANT_VALUE"
],
"to": "snake_case"
});
const req = https.request('https://api.apiverve.com/v1/variablenameconverter', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.write(postData);
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/variablenameconverter');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here',
'Content-Type: application/json'
]);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode({
'variables': [
'myVariableName',
'another_var_name',
'SomeClassName',
'kebab-case-name',
'CONSTANT_VALUE'
],
'to': 'snake_case'
}));
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($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))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/variablenameconverter')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
payload = {
"variables": [
"myVariableName",
"another_var_name",
"SomeClassName",
"kebab-case-name",
"CONSTANT_VALUE"
],
"to": "snake_case"
}
request = Net::HTTP::Post.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'
request.body = payload.to_json
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main(string[] args)
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");
var jsonContent = @"{
""variables"": [
""myVariableName"",
""another_var_name"",
""SomeClassName"",
""kebab-case-name"",
""CONSTANT_VALUE""
],
""to"": ""snake_case""
}";
var content = new StringContent(jsonContent, Encoding.UTF8, "application/json");
var response = await client.PostAsync("https://api.apiverve.com/v1/variablenameconverter", content);
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}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:
Example Responses
{
"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"
}
}<?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
Required and optional headers for Variable Name Converter API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
X-API-Key | required | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
Accept | optional | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
User-Agent | optional | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
X-Request-ID | optional | req_123456789 | Custom request identifier for tracking and debugging requests |
Cache-Control | optional | no-cache | Control caching behavior for the request and response |
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 supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Variable Name Converter directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
Access-Control-Allow-Origin | * | Accepts requests from any origin |
Access-Control-Allow-Methods | * | Accepts any HTTP method |
Access-Control-Allow-Headers | * | Accepts any request headers |
Browser Usage: You can call Variable Name Converter directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
Variable Name Converter API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Variable Name Converter users.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - standard traffic priority |
| Pro | No Limit | Production ready - preferred traffic priority |
| Mega | No Limit | Production ready - highest traffic priority |
Learn more about rate limiting →
Rate Limit Headers
When rate limits apply, each Variable Name Converter response includes headers to help you track your usage:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per time window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, Variable Name Converter returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.
Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.
Best Practices for Variable Name Converter:
- Monitor the rate limit headers to track your Variable Name Converter usage (Free plan only)
- Cache variable name converter responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle Variable Name Converter performance
Note: Variable Name Converter rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Variable Name Converter on Free tier.
Error Codes
The Variable Name Converter API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
200 | OK | Request successful, data returned | No action needed - request was successful |
400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
503 | Service Unavailable | API temporarily unavailable | Wait and retry, check status page for maintenance updates |
Learn more about error handling →
Need help? Contact support with your X-Request-ID for assistance.
Integrate Variable Name Converter with SDKs
Get started quickly with official Variable Name Converter SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.
Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.
Integrate Variable Name Converter with No-Code API Tools
Connect the Variable Name Converter API to your favorite automation platform without writing code. Build workflows that leverage variable name converter data across thousands of apps.





All platforms use your same API key to access Variable Name Converter. Visit our integrations hub for step-by-step 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.



