Source
Configuration
Standard obfuscator.io preset.
Advanced options
Output
Run the pipeline to generate output.
—
—
—
—
Encryption & processing · serverObfuscation · browser
Send JSON requests to this service. Authenticated servers require an X-API-Key header or a Bearer token.
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/encrypt | Encrypt source and return its decrypt script. |
| POST | /api/process-template | Wrap JavaScript in a processed HTML template. |
| POST | /api/process | Run the server stages; accepts encrypted or processed output. |
| GET | /api/options | Available stages, presets, content types and defaults. |
| GET | /api/health | Service availability. |
Encryption request
{ "content": "<h1>Hello</h1>", "content_type": "html", "version": "1.0" }Template function
{ "code": "…JavaScript…", "login_function": "getLoginEmail" }Email is optional. The processed endpoints accept an optional login_function global name or dotted path. Your template can call loginemail() or login_mail() to invoke that function. Without a function, loginemail() returns the optional email or an empty string.
Obfuscation runs in the browser between encryption and template processing. API clients can run their own JavaScript obfuscator between those endpoints.
Required only when server authentication is enabled. The key is sent to this service with pipeline requests and stays in memory for this page. It is not saved in browser storage.
Return to process template