Base64 Encoder/Decoder API

Overview

To use Base64 Encoder/Decoder, 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/base64

Example

How to call the Base64 Encoder/Decoder API in different programming languages.

curl -X GET \
  "https://api.apiverve.com/v1/base64?text=Hello%20World&action=encode" \
  -H "X-API-Key: your_api_key_here"

const response = await fetch('https://api.apiverve.com/v1/base64?text=Hello%20World&action=encode', {
  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/base64?text=Hello%20World&action=encode', 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/base64?text=Hello%20World&action=encode", 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": {
    "action": "encode",
    "original": "Hello World",
    "encoded": "SGVsbG8gV29ybGQ=",
    "length": 16
  }
}

Authentication

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

X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

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

Parameters

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

Response

The Base64 Encoder/Decoder 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>
    <action>encode</action>
    <original>Hello World</original>
    <encoded>SGVsbG8gV29ybGQ=</encoded>
    <length>16</length>
  </data>
</response>

status: ok
error: null
data:
  action: encode
  original: Hello World
  encoded: SGVsbG8gV29ybGQ=
  length: 16

Response Structure

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

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

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 Base64 Encoder/Decoder through GraphQL to combine it with other API calls in a single request. Query only the base64 encoder/decoder 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/graphql

query {
  base64(
    input: {
      text: "Hello World"
      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 Base64 Encoder/Decoder 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

Base64 Encoder/Decoder 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 Base64 Encoder/Decoder 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 Base64 Encoder/Decoder

Official Base64 Encoder/Decoder packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

JitPack

No-Code Integrations

Base64 Encoder/Decoder works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Zapier

Make

Pipedream

n8n

Power Automate

Frequently Asked Questions

People who used this also used...

Based on your interest in Base64 Encoder/Decoder, you might also like these APIs:

XML to JSON

XML to JSON is a simple tool for converting XML to JSON. It returns the JSON representation of the XML provided.

1 credit per call

Words to Numbers

Words to Numbers is a simple tool for converting words to numbers. It returns the words in numbers.

1 credit per call

Website to Text

Website to Text is a simple tool for converting a website to text. It returns the text extracted from the website.

10 credits per call