Overview
FastEdge applications combine a WebAssembly binary with configuration, environment variables, and secrets for deployment at the CDN edge. Apps can be in various states (draft, enabled, disabled) and support debugging, logging, and custom response headers.Create App
Add a new FastEdge application.Parameters
Application name
Binary ID - references a WebAssembly binary to use
Application description or comment
Status code:
0- draft (inactive)1- enabled2- disabled
Template ID to use for the application
Switch on logging for 30 minutes (switched off by default)
Logging channel. Options:
kafka (default, allows exploring logs with API), noneEnvironment variables as key-value pairs
Extra headers to add to responses
Application secrets mapping. Each entry contains:
id(int64, required) - The unique identifier of the secret
Application edge stores mapping. Each entry contains:
id(int64, required) - The identifier of the store
Response
Returns anAppShort object with the created application details.
Application ID
Application name
Binary ID
Application status code
Application URL for accessing the edge app
WebAssembly API type
Application plan ID
Application plan name
Description of the application
Whether debug mode is enabled
When debugging finishes (ISO 8601 format)
List of networks the app is deployed to
Template ID
Template name
ID of the binary the app can be upgraded to
Get App Details
Retrieve detailed information about a specific application.Parameters
The application ID
Response
Returns a fullApp object with all configuration details including environment variables, secrets, stores, and headers.
Application name
Binary ID
WebAssembly API type
Status code
Application description
Debug mode status
Debug expiration timestamp
Logging channel (
kafka or none)Environment variables
Custom response headers
Application secrets with details
Application edge stores with details
Plan name
Plan ID
Template ID
Template name
Application URL
Deployed networks
List Apps
List all applications for the client with optional filtering and pagination.Query Parameters
Filter by application name
Filter by status code (0-5)
Filter by binary ID
Filter by template ID
Filter by plan ID
Filter by API type:
wasi-http- WASI with HTTP entry pointproxy-wasm- Proxy-Wasm app, callable from CDN
Maximum number of results (pagination)
Offset for pagination
Sort order. Options:
name, -name, status, -status, id, -id, template, -template, binary, -binary, plan, -planUse - prefix for descending orderResponse
Returns a paginated list ofAppShort objects.
Auto-Paging
For convenience, you can useListAutoPaging to automatically iterate through all pages:
Update App
Partially update an existing application (PATCH).Parameters
The application ID
Application fields to update. Only provided fields will be updated (partial update).
Accepts the same parameters as the Create App endpoint.
Response
Returns the updatedAppShort object.
Replace App
Fully replace an application’s configuration (PUT).Parameters
The application ID
Complete application configuration. All fields should be provided for a full replacement.
Response
Returns the replacedAppShort object.
Delete App
Delete an application permanently.Parameters
The application ID to delete
Response
Returnsnil on success, or an error if the deletion fails.
Application Logs
Access application logs through theLogs sub-service. See the App Logs documentation for details.
API Types
FastEdge supports two WebAssembly API types:WASI-HTTP
WASI with HTTP entry point - suitable for applications that need to handle HTTP requests directly.Proxy-Wasm
Proxy-Wasm applications that can be called from the CDN layer, allowing integration with CDN features.Best Practices
Environment variables and secrets are distinct - use secrets for sensitive values like API keys that should be stored securely.
