URL Encoder/DecoderURL Encoder/Decoder API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 192ms|p50: 185ms|p75: 197ms|p90: 210ms|p99: 238ms

URL Encoder/Decoder is a tool for encoding and decoding URL strings. It converts special characters to percent-encoded format and decodes them back for safe URL transmission.

The URL Encoder/Decoder API provides reliable and fast access to url encoder/decoder data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.

To use URL Encoder/Decoder, you need an API key. You can get one by creating a free account and visiting your dashboard.

POST Endpoint

URL
https://api.apiverve.com/v1/urlencode

Code Examples

Here are examples of how to call the URL Encoder/Decoder API in different programming languages:

cURL Request
curl -X POST \
  "https://api.apiverve.com/v1/urlencode" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "Hello World & Goodbye",
  "action": "encode"
}'
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/urlencode', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "text": "Hello World & Goodbye",
    "action": "encode"
})
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

payload = {
    "text": "Hello World & Goodbye",
    "action": "encode"
}

response = requests.post('https://api.apiverve.com/v1/urlencode', headers=headers, json=payload)

data = response.json()
print(data)
Node.js (Native HTTPS)
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({
  "text": "Hello World & Goodbye",
  "action": "encode"
});

const req = https.request('https://api.apiverve.com/v1/urlencode', options, (res) => {
  let data = '';
  res.on('data', (chunk) => data += chunk);
  res.on('end', () => console.log(JSON.parse(data)));
});

req.write(postData);
req.end();
PHP (cURL)
<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/urlencode');
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({
    'text': 'Hello World & Goodbye',
    'action': 'encode'
}));

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);
print_r($data);

?>
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"
    "bytes"
    "encoding/json"
)

func main() {
    payload := map[string]interface{}{
        "text": "Hello World & Goodbye",
        "action": "encode"
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/urlencode", 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))
}
Ruby (Net::HTTP)
require 'net/http'
require 'json'

uri = URI('https://api.apiverve.com/v1/urlencode')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

payload = {
  "text": "Hello World & Goodbye",
  "action": "encode"
}

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))
C# (HttpClient)
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 = @"{
        ""text"": ""Hello World & Goodbye"",
        ""action"": ""encode""
}";
        var content = new StringContent(jsonContent, Encoding.UTF8, "application/json");

        var response = await client.PostAsync("https://api.apiverve.com/v1/urlencode", content);
        response.EnsureSuccessStatusCode();

        var responseBody = await response.Content.ReadAsStringAsync();
        Console.WriteLine(responseBody);
    }
}

Authentication

The URL Encoder/Decoder API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the URL Encoder/Decoder API directly in your browser with live requests and responses.

Parameters

The URL Encoder/Decoder API supports multiple query options. Use one of the following:

Option 1: URL Encode

ParameterTypeRequiredDescriptionDefaultExample
textstringrequired
The text to encode
-Hello World!
actionstringoptional
The action to perform
Supported values: encodedecode
encodeencode

Option 2: URL Decode

ParameterTypeRequiredDescriptionDefaultExample
textstringrequired
The URL-encoded string to decode
-Hello%20World%21
actionstringoptional
The action to perform
Supported values: encodedecode
encodedecode

Response

The URL Encoder/Decoder API returns responses in JSON, XML, YAML, and CSV formats:

Example Responses

JSON Response
200 OK
{
  "status": "ok",
  "error": null,
  "data": {
    "action": "encode",
    "original": "Hello World & Goodbye",
    "encoded": "Hello%20World%20%26%20Goodbye",
    "length": 29
  }
}
XML Response
200 OK
<?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>
    <action>encode</action>
    <original>Hello World &amp; Goodbye</original>
    <encoded>Hello%20World%20%26%20Goodbye</encoded>
    <length>29</length>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  action: encode
  original: Hello World & Goodbye
  encoded: Hello%20World%20%26%20Goodbye
  length: 29
CSV Response
200 OK
keyvalue
actionencode
originalHello World & Goodbye
encodedHello%20World%20%26%20Goodbye
length29

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains 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:

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
actionstring"encode"The encoding or decoding action that was performed
originalstring"Hello World & Goodbye"The original text input before encoding or decoding
encodedstring"Hello%20World%20%26%20Goodbye"The resulting encoded or decoded text output
lengthPremiumnumber29The total character length of the encoded or decoded output

Headers

Required and optional headers for URL Encoder/Decoder API requests:

Header NameRequiredExample ValueDescription
X-API-Keyrequiredyour_api_key_hereYour APIVerve API key. Found in your dashboard under API Keys.
Acceptoptionalapplication/jsonSpecify response format: application/json (default), application/xml, or application/yaml
User-AgentoptionalMyApp/1.0Identifies your application for analytics and debugging purposes
X-Request-IDoptionalreq_123456789Custom request identifier for tracking and debugging requests
Cache-Controloptionalno-cacheControl caching behavior for the request and response

Learn more about request headers →

GraphQL AccessALPHA

Access URL Encoder/Decoder through GraphQL to combine it with other API calls in a single request. Query only the url encoder/decoder data you need with precise field selection, and orchestrate complex data fetching workflows.

Test URL Encoder/Decoder in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  urlencode(
    input: {
      text: "Hello World & Goodbye"
      action: "encode"
    }
  ) {
    action
    original
    encoded
    length
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The URL Encoder/Decoder API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call URL Encoder/Decoder directly from browser-based applications without proxy servers.

CORS HeaderValueDescription
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 URL Encoder/Decoder directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.

Learn more about CORS support →

Rate Limiting

URL Encoder/Decoder API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all URL Encoder/Decoder users.

PlanRate LimitDescription
Free5 requests/minHard rate limit enforced - exceeding will return 429 errors
StarterNo LimitProduction ready - standard traffic priority
ProNo LimitProduction ready - preferred traffic priority
MegaNo LimitProduction ready - highest traffic priority

Learn more about rate limiting →

Rate Limit Headers

When rate limits apply, each URL Encoder/Decoder response includes headers to help you track your usage:

HeaderDescription
X-RateLimit-LimitMaximum number of requests allowed per time window
X-RateLimit-RemainingNumber of requests remaining in the current window
X-RateLimit-ResetUnix timestamp when the rate limit window resets

Handling Rate Limits

Free Plan: When you exceed your rate limit, URL Encoder/Decoder 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 URL Encoder/Decoder:

  • Monitor the rate limit headers to track your URL Encoder/Decoder usage (Free plan only)
  • Cache url encoder/decoder responses where appropriate to reduce API calls
  • Upgrade to Pro or Mega for guaranteed no-throttle URL Encoder/Decoder performance

Note: URL Encoder/Decoder rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using URL Encoder/Decoder on Free tier.

Error Codes

The URL Encoder/Decoder API uses standard HTTP status codes to indicate success or failure:

CodeMessageDescriptionSolution
200OKRequest successful, data returnedNo action needed - request was successful
400Bad RequestInvalid request parameters or malformed requestCheck required parameters and ensure values match expected formats
401UnauthorizedMissing or invalid API keyInclude x-api-key header with valid API key from dashboard
403ForbiddenAPI key lacks permission or insufficient creditsCheck credit balance in dashboard or upgrade plan
429Too Many RequestsRate limit exceeded (Free: 5 req/min)Implement request throttling or upgrade to paid plan
500Internal Server ErrorServer error occurredRetry request after a few seconds, contact support if persists
503Service UnavailableAPI temporarily unavailableWait 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 URL Encoder/Decoder with SDKs

Get started quickly with official URL Encoder/Decoder 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 URL Encoder/Decoder with No-Code API Tools

Connect the URL Encoder/Decoder API to your favorite automation platform without writing code. Build workflows that leverage url encoder/decoder data across thousands of apps.

All platforms use your same API key to access URL Encoder/Decoder. Visit our integrations hub for step-by-step setup guides.

Frequently Asked Questions

How do I get an API key for URL Encoder/Decoder?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for URL Encoder/Decoder and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does URL Encoder/Decoder cost?

Each successful URL Encoder/Decoder 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 url encoder/decoder lookups.

Can I use URL Encoder/Decoder in production?

The free plan is for testing and development only. For production use of URL Encoder/Decoder, 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 URL Encoder/Decoder from a browser?
Yes! The URL Encoder/Decoder API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my URL Encoder/Decoder credit limit?

When you reach your monthly credit limit, URL Encoder/Decoder 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.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?