PDF API: Return PDF as URL Instead of Base64 File

What's New

The PDF API can now return PDFs as URLs instead of base64-encoded strings, enabling seamless integration when saving generated PDFs back to Tadabase from API calls.

Before vs. After

Before: Base64 Encoding

Previously, the PDF API returned PDFs as base64-encoded strings:

• Large, unwieldy data payloads
• Required decoding before use
• Difficult to save directly to file fields
• Complex integration workflow

After: URL Response

Now PDFs can be returned as direct URLs:

• Clean, simple URL reference
• Direct file access
• Easy to save to Tadabase file fields
• Streamlined integration

Primary Use Case: Save PDF Back to Tadabase

This feature is specifically designed for API workflows where you:

1. Generate a PDF via API
2. Need to save that PDF back to a Tadabase file field
3. Want to avoid base64 encoding/decoding complexity

Example Workflow

API Integration Example

How to Use

When calling the PDF API, specify that you want a URL response instead of base64. Check the API documentation for the specific parameter to include in your request.

Backward Compatibility

The base64 response format is still available. This is an optional enhancement - existing integrations using base64 continue to work without changes.