Endpoint URL:

https://aisenseapi.com/services/v1/base64_decode

Description:

This endpoint decodes a Base64-encoded string back into its original format. It accepts input as JSON with a data field containing the Base64-encoded string or as raw text with Content-Type: text/plain. The response format supports JSON (default) or raw binary output based on the Accept header.

If the input is invalid, an appropriate error message will be returned.

Response Format

• Content-Type: application/json (default) or application/octet-stream (for binary data)

Example Success Responses

Decoded JSON Data (when Base64 contains JSON)

Decoded Binary Data (when Base64 contains raw binary or non-JSON text)

Binary Output (when Accept: application/octet-stream is set)

The API streams the raw binary data directly to the client.

Example Error Responses

Input Requirements

• Input can be sent as JSON: json
  
  { "data": "SGVsbG8gd29ybGQ=" }

• Or as plain text with Content-Type: text/plain:
  
  SGVsbG8gd29ybGQ=


Use Cases

• Decoding Base64-encoded JSON data for API responses
• Reverting encoded binary files to their original format
• Processing Base64-encoded text data stored in communication protocols
• Temporary storage of decoded binary files with UUID retrieval

How to Use

1. Send a POST request to

2. Choose your input format

• JSON input: json
  
  { "data": "SGVsbG8gd29ybGQ=" }

• Plain text input:
  
  SGVsbG8gd29ybGQ=


3. Specify the desired response format

• JSON response (default):
  Add the header Accept: application/json
• Binary response:
  Add the header Accept: application/octet-stream

4. Handle the response

• If the input is valid JSON, the decoded data is returned directly.
• If the decoded data is binary or non-JSON text, it is stored, and a storage URL is returned instead.
• If the client requests binary output, the decoded data is streamed.

Example cURL Requests

JSON Input with JSON Response

Plain Text Input with Binary Response

Key Features

• Supports both JSON and plain text Base64 input
• Flexible output: JSON (default) or binary based on the Accept header
• Provides temporary storage for large or non-JSON data, retrievable via UUID
• Ensures clear error handling for invalid input or unsupported formats
• No authentication required – free public API