Overview
Custom endpoints are dispatched through a dedicated URL namespace:Key Features
- No Code Required: Define endpoints via API or Admin UI
- Path Parameters: Support for
:paramsegments (e.g.,/users/:user_id/orders) - Authorization Conditions: Gate access with rule expressions
- Action Pipelines: Chain multiple actions with access to results from previous steps
- Response Templates: Customize response status, body, and headers
- Execution History: Track every invocation with timing and status
How It Works
Endpoint Definition
Path Parameters
Use:param syntax to capture path segments:
{{request.params.user_id}} and {{request.params.order_id}} in action templates.
Uniqueness
Each endpoint is uniquely identified by the combination of(account_id, path, method). You cannot create two endpoints with the same path and method within one account.
Actions
Actions execute sequentially. Each action’s result is available to subsequent actions.Supported Action Types
Query Records
Aggregate Records
count, sum, avg, min, max.
Transform
Reshape data from previous action results:Template Variables
All string values in action configs and response templates support these variables:Response Templates
Customize what your endpoint returns:Authorization
Authentication
Setauth_required: true (the default) to require a valid authentication token. Set to false for public endpoints.
Condition Expressions
Add acondition to control who can access the endpoint:
false, the endpoint returns 403 Forbidden.