Base64 Encoder/Decoder API GET

Base64 Encoder/Decoder is a simple tool for encoding and decoding Base64 strings. It supports both encoding text to Base64 and decoding Base64 back to text.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/base64

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Base64 Encoder/Decoder response payload
  }
}

About the Base64 Encoder/Decoder API

Base64 Encoder/Decoder works by converting text to Base64 encoding or decoding Base64 strings back to readable text. Returns the converted result along with length information.

What people use it for

Data Transmission: Encode binary data as Base64 for safe transmission over text-based protocols like email or HTTP
API Integration: Encode credentials or sensitive data in Base64 format for API authentication headers
File Embedding: Encode images or files as Base64 strings to embed them directly in HTML, CSS, or JSON
Data Storage: Convert binary data to Base64 for storage in text-based databases or configuration files

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Base64 Encoder/Decoder

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets

Questions.

Common questions about the Base64 Encoder/Decoder API.

Read the docs →

What does the Base64 Encoder/Decoder API do?

Base64 Encoder/Decoder is a simple tool for encoding and decoding Base64 strings. It supports both encoding text to Base64 and decoding Base64 back to text.

How do I authenticate Base64 Encoder/Decoder API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Base64 Encoder/Decoder API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Base64 Encoder/Decoder API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Base64 Encoder/Decoder API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Base64 Encoder/Decoder API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/base64

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`text`Required	string	`Hello World`	The text to encode

Optional

Parameter	Type	Example	Description
`action`Optional	string	`encode`	The action to perform `encodedecode` default encode

Example request

1
2

curl "https://api.apiverve.com/v1/base64?text=Hello%20World&action=encode" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/base64

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

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

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`action`	string	`"encode"`	The action performed on the text
`original`	string	`"Hello World"`	The original input text before encoding
`encoded`	string	`"SGVsbG8gV29ybGQ="`	The Base64 encoded result of the input text
`length`	number	`16`	Length of the original input text

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Base64 Encoder/Decoder calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/base64

No SDK to install — this is a plain HTTPS call to /v1/base64 with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/base64" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/base64-apiSource, issues and the examples this page is built from.ReferenceBase64 Encoder/Decoder API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/base64npm APIVerve.API.Base64EncoderDecoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/base64

Install the Node.js SDK, then call the Base64 Encoder/Decoder API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/base64

Node.js

const res = await fetch("https://api.apiverve.com/v1/base64", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/base64The published Node.js client, versioned and signed.GitHubapiverve/base64-apiSource, issues and the examples this page is built from.ReferenceBase64 Encoder/Decoder API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.Base64EncoderDecoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/base64

No SDK to install — this is a plain HTTPS call to /v1/base64 with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/base64",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/base64npm APIVerve.API.Base64EncoderDecoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/base64

Install the C# / .NET SDK, then call the Base64 Encoder/Decoder API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.Base64EncoderDecoder

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/base64");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.Base64EncoderDecoderThe published C# / .NET client, versioned and signed.GitHubapiverve/base64-apiSource, issues and the examples this page is built from.ReferenceBase64 Encoder/Decoder API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/base64npm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/base64

No SDK to install — this is a plain HTTPS call to /v1/base64 with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/base64", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/base64npm APIVerve.API.Base64EncoderDecoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/base64

No SDK to install — this is a plain HTTPS call to /v1/base64 with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/base64");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

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

Resources

Also published for

@apiverve/base64npm APIVerve.API.Base64EncoderDecoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/base64

No SDK to install — this is a plain HTTPS call to /v1/base64 with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/base64")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/base64npm APIVerve.API.Base64EncoderDecoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Data Conversion

View all 33 →

All articles →

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

Generate PDFs from HTML with an APIConvert HTML to PDF programmatically. Tutorial covering invoices, reports, receipts, and certificates with code examples.Read

Automating Visual Testing With ScreenshotsCatch visual bugs before users do. Here's how to add screenshot-based testing to your workflow.Read

Base64 Encoder/Decoder API GET

Try it — live request, no key required

About the Base64 Encoder/Decoder API

What people use it for

Ways to call it

Other ways to use Base64 Encoder/Decoder

Questions.

Request parameters — GET /v1/base64

Required

Optional

Authentication

Response — GET /v1/base64

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/base64

Resources

Also published for

Call it from Node.js — GET /v1/base64

Resources

Also published for

Call it from Python — GET /v1/base64

Resources

Also published for

Call it from C# / .NET — GET /v1/base64

Resources

Also published for

Call it from Go — GET /v1/base64

Resources

Also published for

Call it from PHP — GET /v1/base64

Resources

Also published for

Call it from Ruby — GET /v1/base64

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Base64 Encoder/Decoder API

Data Conversion

Related articles

Ready to build with Base64 Encoder/Decoder? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog