PHP API Reference
PHP API Reference v0.17.0¶
Functions¶
schemaQueryOnly()¶
Create a simple schema configuration with only Query type.
This is a convenience function for schemas that only have queries.
Returns:
A QueryOnlyConfig with default settings
Signature:
Example:
Returns: QueryOnlyConfig
schemaQueryMutation()¶
Create a schema configuration with Query and Mutation types.
This is a convenience function for schemas with queries and mutations but no subscriptions.
Returns:
A QueryMutationConfig with default settings
Signature:
Example:
Returns: QueryMutationConfig
schemaFull()¶
Create a schema configuration with all three root types.
This is a convenience function for fully-featured schemas.
Returns:
A FullSchemaConfig with default settings
Signature:
Example:
Returns: FullSchemaConfig
Types¶
ApiKeyAuthConfig¶
Per-route API key authentication requirement.
Mirrors spikard_http::ApiKeyConfig for the same reason JwtAuthConfig mirrors
spikard_http::JwtConfig: spikard-core cannot depend on spikard-http.
| Field | Type | Default | Description |
|---|---|---|---|
enabled |
bool |
true |
Whether this per-route API key auth requirement is active. Present on 10/10 api_key_auth fixture payloads in the corpus; defaults to true for the same reason as JwtAuthConfig::enabled. |
keys |
array<string> |
/* serde(default) */ |
Valid API keys. Defaults to empty (rather than being a required field) so that fixtures/server_config.json's server_jwt_and_api_key_auth_combined payload ({"enabled": true, "header": "X-API-Key"}, no keys at all) deserializes instead of hard-failing with "missing field keys". An empty list is NOT "allow everyone": a later enforcement phase MUST treat an empty keys list as a hard misconfiguration error, never as an open gate. |
headerName |
string |
"X-API-Key" |
Header name to check (e.g., "X-API-Key") |
ApiKeyConfig¶
API Key authentication configuration
| Field | Type | Default | Description |
|---|---|---|---|
keys |
array<string> |
— | Valid API keys |
headerName |
string |
"X-API-Key" |
Header name to check (e.g., "X-API-Key") |
AsyncApiConfig¶
AsyncAPI HTTP endpoint configuration
| Field | Type | Default | Description |
|---|---|---|---|
enabled |
bool |
— | Enable AsyncAPI endpoints (default: false) |
spec |
?mixed |
null |
Pre-registered AsyncAPI spec to serve from GET /asyncapi.json |
AuthorizationConfig¶
Per-route roles/scopes/permissions authorization requirement.
spikard_http::auth::Claims does not yet carry roles, scopes, or permissions, so nothing can
enforce this today. This type only defines the requirement shape; a later phase must extend
Claims (or an equivalent claims-decoding path) to populate them before enforcement is
possible.
Deserialization goes through AuthorizationConfigRepr rather than a derive so the fixture's
singular {"required_role": "admin"} shape (fixtures/problem_details.json's
problem_details_403_forbidden) populates required_roles instead of being silently dropped
as an unrecognized field — a config that parses to "no constraint" from real authorization
data is a vacuous-pass bug, not a compatibility shim. deny_unknown_fields on the repr means
any other unrecognized key is a loud deserialize error instead.
| Field | Type | Default | Description |
|---|---|---|---|
requiredRoles |
array<string> |
[] |
Roles the authenticated caller must have |
requiredScopes |
array<string> |
[] |
OAuth-style scopes the authenticated caller must have |
requiredPermissions |
array<string> |
[] |
Fine-grained permissions the authenticated caller must have |
requireAll |
bool |
true |
When true, the caller must satisfy every listed requirement (AND); when false, any single listed requirement is sufficient (OR) |
BackgroundJobMetadata¶
| Field | Type | Default | Description |
|---|---|---|---|
name |
string |
"background_task" |
The name |
requestId |
?string |
null |
Request id |
BackgroundTaskConfig¶
Configuration for in-process background task execution.
| Field | Type | Default | Description |
|---|---|---|---|
enabled |
bool |
false |
Whether the server starts a background task executor at router-construction time. ServerConfig.background_tasks is a bare struct rather than an Option, so its mere presence cannot mean "configured" the way Option-shaped middleware config does — every server has one. Without this flag every router build would spawn an executor task, which also requires an ambient Tokio runtime that a synchronous build_router_* caller may not have. Defaults to false so opting in is explicit, and matches the corpus vocabulary: fixtures/background_tasks.json spells its per-route payloads {"enabled": true, ...}. |
maxQueueSize |
int |
1024 |
Maximum queue size |
maxConcurrentTasks |
int |
128 |
Maximum concurrent tasks |
drainTimeoutSecs |
int |
30 |
Drain timeout secs |
CompressionConfig¶
Compression configuration shared across runtimes
| Field | Type | Default | Description |
|---|---|---|---|
gzip |
bool |
true |
Enable gzip compression |
brotli |
bool |
true |
Enable brotli compression |
minSize |
int |
1024 |
Minimum response size to compress (bytes) |
quality |
int |
6 |
Compression quality (0-11 for brotli, 0-9 for gzip) |
ContactInfo¶
Contact information
| Field | Type | Default | Description |
|---|---|---|---|
name |
?string |
null |
Name of the contact person or organisation. |
email |
?string |
null |
Contact email address. |
url |
?string |
null |
URL pointing to the contact information page. |
CorsConfig¶
CORS configuration for a route
| Field | Type | Default | Description |
|---|---|---|---|
allowedOrigins |
array<string> |
["*"] |
Allowed origins |
allowedMethods |
array<string> |
["*"] |
Allowed methods |
allowedHeaders |
array<string> |
[] |
Allowed headers |
exposeHeaders |
?array<string> |
null |
Expose headers |
maxAge |
?int |
null |
Maximum age |
allowCredentials |
?bool |
null |
Allow credentials |
DynamicSchemaConfig¶
Configuration for building and executing a dynamic-SDL schema.
| Field | Type | Default | Description |
|---|---|---|---|
introspectionEnabled |
bool |
— | Whether introspection queries (__schema, __type) are permitted. |
maxComplexity |
?int |
null |
Maximum query complexity (null = unlimited). |
maxDepth |
?int |
null |
Maximum query depth (null = unlimited). |
fieldErrors |
array<FieldErrorSpec> |
[] |
Field-level errors to inject at specific response paths. |
FieldErrorSpec¶
A field-level error to inject at a specific response path.
path is the dot-separated sequence of field names from the operation root to the field
that should fail, e.g. "user" for a top-level field or "order.customer" for a nested one.
| Field | Type | Default | Description |
|---|---|---|---|
path |
string |
— | Dot-separated path to the field that should error. |
message |
string |
— | The error message to surface for that field. |
FullSchemaConfig¶
Configuration for fully-featured schemas with Query, Mutation, and Subscription types
| Field | Type | Default | Description |
|---|---|---|---|
introspectionEnabled |
bool |
true |
Enable introspection queries |
complexityLimit |
?int |
null |
Maximum query complexity (None = unlimited) |
depthLimit |
?int |
null |
Maximum query depth (None = unlimited) |
GraphQlRouteConfig¶
Configuration for GraphQL routes
Provides a builder pattern for configuring GraphQL route parameters for the Spikard HTTP server's routing system.
Methods¶
new()¶
Create a new GraphQL route configuration with defaults
Default values:
- path: "/graphql"
- method: "POST"
enable_playground: false
Signature:
Example:
Returns: GraphQlRouteConfig
path()¶
Set the HTTP path for the GraphQL endpoint
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
path |
string |
Yes | The URL path (e.g., "/graphql", "/api/graphql") |
Returns: GraphQlRouteConfig
method()¶
Set the HTTP method for the GraphQL endpoint
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
method |
string |
Yes | The HTTP method (typically "POST") |
Returns: GraphQlRouteConfig
enablePlayground()¶
Enable or disable the GraphQL Playground UI
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
enable |
bool |
Yes | Whether to enable playground |
Returns: GraphQlRouteConfig
description()¶
Set a custom description for documentation
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
description |
string |
Yes | Documentation string |
Returns: GraphQlRouteConfig
getPath()¶
Get the configured path
Signature:
Example:
Returns: string
getMethod()¶
Get the configured method
Signature:
Example:
Returns: string
isPlaygroundEnabled()¶
Check if playground is enabled
Signature:
Example:
Returns: bool
getDescription()¶
Get the description if set
Signature:
Example:
Returns: ?string
GraphQlSubscriptionSnapshot¶
Snapshot of a GraphQL subscription exchange over WebSocket.
Derives Serialize so language bindings (e.g. the JNI backend) can marshal it
across the FFI boundary via serde_json without a hand-written wrapper.
| Field | Type | Default | Description |
|---|---|---|---|
operationId |
string |
— | Operation id used for the subscription request. |
acknowledged |
bool |
— | Whether the server acknowledged the GraphQL WebSocket connection. |
event |
?mixed |
null |
First next.payload received for this subscription, if any. |
errors |
array<mixed> |
[] |
GraphQL protocol errors emitted by the server. |
completeReceived |
bool |
— | Whether a complete frame was observed for this operation. |
GrpcConfig¶
Configuration for gRPC support
Controls how the server handles gRPC requests, including compression, timeouts, and protocol settings.
Stream Limits¶
This configuration enforces message-level size limits but delegates concurrent stream limiting to the HTTP/2 transport layer:
-
Message Size Limits: The
max_message_sizefield is enforced per individual message (request or response) in both unary and streaming RPCs. When a single message exceeds this limit, the request is rejected withPAYLOAD_TOO_LARGE(HTTP 413). -
Concurrent Stream Limits: The
max_concurrent_streamsis an advisory configuration passed to the HTTP/2 layer for connection-level stream negotiation. The HTTP/2 transport automatically enforces this limit and returns GOAWAY frames when exceeded. Applications should not rely on custom enforcement of this limit. -
Stream Response Size Limits: The
max_stream_response_bytesfield caps the total encoded bytes emitted across a server-streaming or bidi-streaming response. When the cumulative size exceeds the limit, the stream is terminated withtonic::Status::resource_exhausted. Defaults tonull(unbounded).
| Field | Type | Default | Description |
|---|---|---|---|
enabled |
bool |
true |
Enable gRPC support |
maxMessageSize |
int |
4194304 |
Maximum message size in bytes (for both sending and receiving) This limit applies to individual messages in both unary and streaming RPCs. When a single message exceeds this size, the request is rejected with HTTP 413 (Payload Too Large). Default: 4MB (4194304 bytes) Note: This limit does NOT apply to the total response size in streaming RPCs. For multi-message streams, the total response can exceed this limit as long as each individual message stays within the limit. |
enableCompression |
bool |
true |
Enable gzip compression for gRPC messages |
requestTimeout |
?int |
null |
Timeout for gRPC requests in seconds (None = no timeout) |
maxConcurrentStreams |
int |
100 |
Maximum number of concurrent streams per connection (HTTP/2 advisory) This value is communicated to HTTP/2 clients as the server's flow control limit. The HTTP/2 transport layer enforces this limit automatically via SETTINGS frames and GOAWAY responses. Applications should NOT implement custom enforcement. Default: 100 streams per connection # Stream Limiting Strategy - Per Connection: This limit applies per HTTP/2 connection, not globally - Transport Enforcement: HTTP/2 handles all stream limiting; applications need not implement custom checks - Streaming Requests: In server streaming or bidi streaming, each logical RPC consumes one stream slot. Message ordering within a stream follows HTTP/2 frame ordering. |
enableKeepalive |
bool |
true |
Enable HTTP/2 keepalive |
keepaliveInterval |
int |
75 |
HTTP/2 keepalive interval in seconds |
keepaliveTimeout |
int |
20 |
HTTP/2 keepalive timeout in seconds |
maxStreamResponseBytes |
?int |
null |
Total byte cap across an entire streaming response. When Some(n), the streaming adapter aborts the stream with tonic::Status::resource_exhausted once the cumulative encoded message bytes exceed n. The stream yields the error item and then terminates. Per-message cap remains max_message_size. This limit applies to server-streaming and bidirectional-streaming RPCs only; unary RPCs are governed solely by max_message_size. Default: null (unbounded total response size). |
IntoHandler¶
Convert user-facing handler functions into the low-level Handler trait.
Methods¶
intoHandler()¶
Convert this value into a shared request handler.
Signature:
Example:
Returns: Handler
JsonRpcConfig¶
JSON-RPC server configuration
| Field | Type | Default | Description |
|---|---|---|---|
enabled |
bool |
true |
Enable JSON-RPC endpoint |
endpointPath |
string |
"/rpc" |
HTTP endpoint path for JSON-RPC requests (default: "/rpc") |
enableBatch |
bool |
true |
Enable batch request processing (default: true) |
maxBatchSize |
int |
100 |
Maximum number of requests in a batch (default: 100) |
JsonRpcMethodInfo¶
JSON-RPC method metadata for routes that support JSON-RPC
This struct captures the metadata needed to expose HTTP routes as JSON-RPC methods, enabling discovery and documentation of RPC-compatible endpoints.
| Field | Type | Default | Description |
|---|---|---|---|
methodName |
string |
— | The JSON-RPC method name (e.g., "user.create") |
description |
?string |
null |
Optional description of what the method does |
paramsSchema |
?mixed |
null |
Optional JSON Schema for method parameters |
resultSchema |
?mixed |
null |
Optional JSON Schema for the result |
deprecated |
bool |
/* serde(default) */ |
Whether this method is deprecated |
tags |
array<string> |
/* serde(default) */ |
Tags for categorizing and grouping methods |
JwtAuthConfig¶
Per-route JWT authentication requirement.
spikard-http defines the canonical JwtConfig used by ServerConfig.jwt_auth, but
spikard-core cannot depend on spikard-http (the dependency runs the other way), so that
type cannot be reused here. This mirrors its fields so a later enforcement phase in
spikard-http can convert between the two without losing information.
secret and public_key are both optional because asymmetric algorithms (RS256, ES256, ...)
verify against a public key rather than a shared secret; see fixtures/auth.json's
jwt_config_algorithm_rs256, which carries public_key and no secret at all. Exactly one is
expected to be populated for a given algorithm, but that cross-field invariant is left to a
later enforcement phase rather than the type itself.
| Field | Type | Default | Description |
|---|---|---|---|
enabled |
bool |
true |
Whether this per-route JWT auth requirement is active. Present on 21/21 jwt_auth fixture payloads in the corpus; defaults to true because presence of a jwt_auth block has always meant "enabled" up to now. Without this field a fixture setting "enabled": false would silently keep auth on while the fixture's parse still succeeds — a vacuous pass. |
secret |
?string |
/* serde(default) */ |
Symmetric secret key for JWT verification (HS256, HS384, HS512) |
publicKey |
?string |
/* serde(default) */ |
Asymmetric public key for JWT verification (RS256, ES256, etc.) |
algorithm |
string |
"HS256" |
Required algorithm (HS256, HS384, HS512, RS256, etc.) |
audience |
?array<string> |
null |
Required audience claim |
issuer |
?string |
null |
Required issuer claim |
leeway |
int |
/* serde(default) */ |
Leeway for expiration checks (seconds) |
JwtConfig¶
JWT authentication configuration
| Field | Type | Default | Description |
|---|---|---|---|
secret |
string |
— | Secret key for JWT verification |
algorithm |
string |
"HS256" |
Required algorithm (HS256, HS384, HS512, RS256, etc.) |
audience |
?array<string> |
null |
Required audience claim |
issuer |
?string |
null |
Required issuer claim |
leeway |
int |
/* serde(default) */ |
Leeway for expiration checks (seconds) |
LicenseInfo¶
License information
| Field | Type | Default | Description |
|---|---|---|---|
name |
string |
— | SPDX license identifier or display name (e.g. "MIT"). |
url |
?string |
null |
URL to the full license text. |
LifecycleHookRef¶
A single lifecycle hook reference within a LifecycleHooksConfig phase.
Matches the fixture shape exactly (fixtures/lifecycle_hooks.json, fixtures/di.json): each
entry is an object with a required name and handler, an optional list of dependency keys,
and an optional free-form config blob (e.g. {"max_requests": 10, "window_seconds": 60} for
a rate-limiting hook). deny_unknown_fields turns future fixture drift into a loud error.
| Field | Type | Default | Description |
|---|---|---|---|
name |
string |
— | Registered name of the hook to run, resolved against the server's LifecycleHooks |
handler |
string |
— | Name of the handler function this hook invokes |
dependencies |
array<string> |
[] |
Dependency keys this hook requires (for DI), resolved before the hook runs |
config |
?mixed |
null |
Optional free-form configuration passed to the hook (e.g. rate-limit thresholds) |
order |
?int |
null |
Explicit execution order within the phase, where the corpus states one (fixtures/lifecycle_hooks.json's hook_execution_order). Array position already implies an order, so this exists to let a fixture assert ordering rather than rely on it. |
LifecycleHooksConfig¶
Per-route selection of registered lifecycle hooks.
ServerConfig.lifecycle_hooks holds Arc<dyn LifecycleHook> function pointers and is marked
#[serde(skip)] / #[alef(skip)] because closures cannot be serialized or cross the FFI
boundary. A per-route field with that same shape would be invisible to alef, and therefore
invisible to every binding — defeating the purpose of exposing it here. This descriptor
carries LifecycleHookRef entries instead: each one names a registered hook (plus its
declared dependencies and optional config), so a later enforcement phase can resolve those
names against the server's registered LifecycleHooks and run the matches for this route. The
five fields mirror the five hook phases documented in the tower-middleware-and-lifecycle
project convention (onRequest, preValidation, preHandler, onResponse, onError).
| Field | Type | Default | Description |
|---|---|---|---|
onRequest |
array<LifecycleHookRef> |
[] |
Hooks to run in the on_request phase |
preValidation |
array<LifecycleHookRef> |
[] |
Hooks to run in the pre_validation phase |
preHandler |
array<LifecycleHookRef> |
[] |
Hooks to run in the pre_handler phase |
onResponse |
array<LifecycleHookRef> |
[] |
Hooks to run in the on_response phase |
onError |
array<LifecycleHookRef> |
[] |
Hooks to run in the on_error phase |
OpenApiConfig¶
OpenAPI configuration
| Field | Type | Default | Description |
|---|---|---|---|
enabled |
bool |
false |
Enable OpenAPI generation (default: false for zero overhead) |
title |
string |
"API" |
API title |
version |
string |
"1.0.0" |
API version |
description |
?string |
null |
API description (supports markdown) |
swaggerUiPath |
string |
"/docs" |
Path to serve Swagger UI (default: "/docs") |
redocPath |
string |
"/redoc" |
Path to serve Redoc (default: "/redoc") |
openapiJsonPath |
string |
"/openapi.json" |
Path to serve OpenAPI JSON spec (default: "/openapi.json") |
contact |
?ContactInfo |
null |
Contact information |
license |
?LicenseInfo |
null |
License information |
servers |
array<ServerInfo> |
[] |
Server definitions |
securitySchemes |
array<string, SecuritySchemeInfo> |
{} |
Security schemes (auto-detected from middleware if not provided) |
ParseRequest¶
Request body for POST /asyncapi/parse
| Field | Type | Default | Description |
|---|---|---|---|
spec |
mixed |
— | Spec |
ParseResult¶
Full parse result returned by POST /asyncapi/parse
| Field | Type | Default | Description |
|---|---|---|---|
specVersion |
string |
— | Spec version |
title |
string |
— | Title |
apiVersion |
string |
— | Api version |
channels |
array<ParsedChannel> |
— | Channels |
operations |
array<ParsedOperation> |
— | Operations |
messages |
array<ParsedMessage> |
— | Messages |
ParsedChannel¶
A single channel extracted from an AsyncAPI spec
| Field | Type | Default | Description |
|---|---|---|---|
name |
string |
— | Channel key from the spec (e.g. "chat/messages") |
address |
string |
— | Channel address / path |
messages |
array<string> |
— | Message names declared on this channel |
bindings |
?mixed |
null |
Bindings (ws / http / amqp / …) as raw JSON for forward-compatibility |
ParsedMessage¶
A resolved message (name + JSON Schema)
| Field | Type | Default | Description |
|---|---|---|---|
name |
string |
— | Message name |
schema |
?mixed |
null |
Resolved JSON Schema for the message payload, if available |
ParsedOperation¶
A single operation extracted from an AsyncAPI spec
| Field | Type | Default | Description |
|---|---|---|---|
name |
string |
— | Operation name |
action |
string |
— | Operation action: "send" or "receive" |
channel |
string |
— | Channel reference (resolved to the channel name) |
ProblemDetails¶
RFC 9457 Problem Details for HTTP APIs
A machine-readable format for specifying errors in HTTP API responses.
Per RFC 9457, all fields are optional. The type field defaults to "about:blank"
if not specified.
Content-Type¶
Responses using this struct should set:
{
"type": "<https://spikard.dev/errors/validation-error>",
"title": "Request Validation Failed",
"status": 422,
"detail": "2 validation errors in request body",
"errors": [...]
}
| Field | Type | Default | Description |
|---|---|---|---|
typeUri |
string |
"about:blank" |
A URI reference that identifies the problem type. Defaults to "about:blank" when absent. Should be a stable, human-readable identifier for the problem type. |
title |
string |
"" |
A short, human-readable summary of the problem type. Should not change from occurrence to occurrence of the problem. |
status |
int |
500 |
The HTTP status code generated by the origin server. This is advisory; the actual HTTP status code takes precedence. |
detail |
?string |
null |
A human-readable explanation specific to this occurrence of the problem. |
instance |
?string |
null |
A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. |
extensions |
array<string, mixed> |
{} |
Extension members - problem-type-specific data. For validation errors, this typically contains an "errors" array. |
QueryMutationConfig¶
Configuration for schemas with Query and Mutation types
| Field | Type | Default | Description |
|---|---|---|---|
introspectionEnabled |
bool |
true |
Enable introspection queries |
complexityLimit |
?int |
null |
Maximum query complexity (None = unlimited) |
depthLimit |
?int |
null |
Maximum query depth (None = unlimited) |
QueryOnlyConfig¶
Configuration for schemas with only Query type
| Field | Type | Default | Description |
|---|---|---|---|
introspectionEnabled |
bool |
true |
Enable introspection queries |
complexityLimit |
?int |
null |
Maximum query complexity (None = unlimited) |
depthLimit |
?int |
null |
Maximum query depth (None = unlimited) |
RateLimitConfig¶
Rate limiting configuration shared across runtimes
| Field | Type | Default | Description |
|---|---|---|---|
perSecond |
int |
100 |
Requests per second |
burst |
int |
200 |
Burst allowance |
ipBased |
bool |
true |
Use IP-based rate limiting |
Request¶
RequestIdConfig¶
Per-route request-id generation/propagation override.
Modeled as a struct rather than Option<bool> on RouteMetadata because the wire shape is an
object, not a bare boolean: fixtures/request_id.json's request_id_middleware_can_be_disabled
sends {"enabled": false}, which Option<bool> cannot deserialize at all ("invalid type: map,
expected a boolean") — the very fixture whose purpose is proving the middleware can be disabled
was the one that failed to parse.
| Field | Type | Default | Description |
|---|---|---|---|
enabled |
bool |
— | Whether request-id generation/propagation is active for this route |
Response¶
HTTP Response with custom status code, headers, and content
| Field | Type | Default | Description |
|---|---|---|---|
content |
?mixed |
null |
Response body content |
statusCode |
int |
200 |
HTTP status code (defaults to 200) |
headers |
array<string, string> |
{} |
Response headers |
ResponseSnapshot¶
Snapshot of an Axum response used by higher-level language bindings.
| Field | Type | Default | Description |
|---|---|---|---|
status |
int |
— | HTTP status code. |
headers |
array<string, string> |
— | Response headers (lowercase keys for predictable lookups). |
body |
string |
— | Response body bytes (decoded for supported encodings). |
RouteBuilder¶
Builder for defining a route.
Methods¶
new()¶
Create a new builder for the provided HTTP method and path.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
method |
Method |
Yes | The method |
path |
string |
Yes | Path to the file |
Returns: RouteBuilder
handlerName()¶
Assign an explicit handler name.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
name |
string |
Yes | The name |
Returns: RouteBuilder
requestSchemaJson()¶
Provide a raw JSON schema for the request body.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
schema |
mixed |
Yes | The schema |
Returns: RouteBuilder
responseSchemaJson()¶
Provide a raw JSON schema for the response body.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
schema |
mixed |
Yes | The schema |
Returns: RouteBuilder
paramsSchemaJson()¶
Provide a raw JSON schema for request parameters.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
schema |
mixed |
Yes | The schema |
Returns: RouteBuilder
fileParamsJson()¶
Provide multipart file parameter configuration.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
schema |
mixed |
Yes | The schema |
Returns: RouteBuilder
cors()¶
Attach a CORS configuration for this route.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
cors |
CorsConfig |
Yes | The cors config |
Returns: RouteBuilder
compression()¶
Attach a compression configuration for this route.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
compression |
CompressionConfig |
Yes | The compression config |
Returns: RouteBuilder
bodyLimit()¶
Attach a per-route maximum request body size in bytes, overriding the server-global default.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
maxBytes |
int |
Yes | The max bytes |
Returns: RouteBuilder
requestTimeout()¶
Attach a per-route request timeout in seconds, overriding the server-global default.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
seconds |
int |
Yes | The seconds |
Returns: RouteBuilder
rateLimit()¶
Attach a per-route rate limiting configuration, overriding the server-global default.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
rateLimit |
RateLimitConfig |
Yes | The rate limit config |
Returns: RouteBuilder
requestId()¶
Force per-route request-id generation on or off, overriding the server-global default.
Takes a plain bool rather than RequestIdConfig directly: the wire/metadata type had
to become a struct to represent {"enabled": false} (see RequestIdConfig's docs), but
this builder is the ergonomic call site (.request_id(true)), so it keeps accepting a bool
and wraps it into RequestIdConfig internally in Self::into_metadata.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
enabled |
bool |
Yes | The enabled |
Returns: RouteBuilder
jwtAuth()¶
Require JWT authentication for this route.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
config |
JwtAuthConfig |
Yes | The configuration options |
Returns: RouteBuilder
apiKeyAuth()¶
Require API key authentication for this route.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
config |
ApiKeyAuthConfig |
Yes | The configuration options |
Returns: RouteBuilder
authorization()¶
Attach a roles/scopes/permissions authorization requirement for this route.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
config |
AuthorizationConfig |
Yes | The configuration options |
Returns: RouteBuilder
lifecycleHooks()¶
Select registered lifecycle hooks to run for this route.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
hooks |
LifecycleHooksConfig |
Yes | The lifecycle hooks config |
Returns: RouteBuilder
jsonrpcMethod()¶
Expose this route as a JSON-RPC method.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
info |
JsonRpcMethodInfo |
Yes | The json rpc method info |
Returns: RouteBuilder
openrpcSpec()¶
Attach a literal OpenRPC method spec document for this route, overriding
auto-derivation from the Self::jsonrpc_method metadata when present.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
spec |
mixed |
Yes | The spec |
Returns: RouteBuilder
sync()¶
Mark the route as synchronous.
Signature:
Example:
Returns: RouteBuilder
handlerDependencies()¶
Declare the dependency keys that must be resolved before this handler runs.
Signature:
Example:
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
dependencies |
array<string> |
Yes | The dependencies |
Returns: RouteBuilder
SchemaConfig¶
Configuration for GraphQL schema building.
Encapsulates all schema-level configuration options including introspection control, complexity limits, and depth limits.
| Field | Type | Default | Description |
|---|---|---|---|
introspectionEnabled |
bool |
true |
Enable introspection queries |
complexityLimit |
?int |
null |
Maximum query complexity (None = unlimited) |
depthLimit |
?int |
null |
Maximum query depth (None = unlimited) |
ServerConfig¶
Server configuration
| Field | Type | Default | Description |
|---|---|---|---|
host |
string |
"127.0.0.1" |
Host to bind to |
port |
int |
8000 |
Port to bind to |
workers |
int |
1 |
Number of Tokio runtime worker threads used by binding-managed server runtimes |
enableRequestId |
bool |
false |
Enable request ID generation and propagation |
maxBodySize |
?int |
10485760 |
Maximum request body size in bytes (None = unlimited, not recommended) |
requestTimeout |
?int |
null |
Request timeout in seconds (None = no timeout) |
compression |
?CompressionConfig |
null |
Enable compression middleware |
rateLimit |
?RateLimitConfig |
null |
Enable rate limiting |
jwtAuth |
?JwtConfig |
null |
JWT authentication configuration |
apiKeyAuth |
?ApiKeyConfig |
null |
API Key authentication configuration |
staticFiles |
array<StaticFilesConfig> |
[] |
Static file serving configuration |
gracefulShutdown |
bool |
true |
Enable graceful shutdown on SIGTERM/SIGINT |
shutdownTimeout |
int |
30 |
Graceful shutdown timeout (seconds) |
asyncapi |
?AsyncApiConfig |
null |
AsyncAPI HTTP endpoint configuration |
openapi |
?OpenApiConfig |
null |
OpenAPI documentation configuration |
jsonrpc |
?JsonRpcConfig |
null |
JSON-RPC configuration |
grpc |
?GrpcConfig |
null |
gRPC configuration |
backgroundTasks |
BackgroundTaskConfig |
— | Background task executor configuration |
enableHttpTrace |
bool |
false |
Enable per-request HTTP tracing (tower-http TraceLayer) |
ServerInfo¶
Server information
| Field | Type | Default | Description |
|---|---|---|---|
url |
string |
— | Base URL of the server (e.g. "<https://api.example.com/v1>"). |
description |
?string |
null |
Optional human-readable description of the server environment. |
SseEvent¶
An individual SSE event
Represents a single Server-Sent Event to be sent to a connected client. Events can have an optional type, ID, and retry timeout for advanced scenarios.
SSE Format¶
Events are serialized to the following text format:
| Field | Type | Default | Description |
|---|---|---|---|
eventType |
?string |
null |
Event type (optional) |
data |
mixed |
— | Event data (JSON value) |
id |
?string |
null |
Event ID (optional, for client-side reconnection) |
retry |
?int |
null |
Retry timeout in milliseconds (optional) |
StaticFilesConfig¶
Static file serving configuration
| Field | Type | Default | Description |
|---|---|---|---|
directory |
string |
— | Directory path to serve |
routePrefix |
string |
— | URL path prefix (e.g., "/static") |
indexFile |
bool |
true |
Fallback to index.html for directories |
cacheControl |
?string |
null |
Cache-Control header value |
TestingSseEvent¶
A single Server-Sent Event.
| Field | Type | Default | Description |
|---|---|---|---|
data |
string |
— | The data field of the event. |
UploadFile¶
Represents an uploaded file from multipart/form-data requests.
This struct provides efficient access to file content with automatic base64 decoding and implements standard I/O traits for compatibility.
| Field | Type | Default | Description |
|---|---|---|---|
filename |
string |
— | Original filename from the client |
contentType |
?string |
null |
MIME type of the uploaded file |
size |
?int |
null |
Size of the file in bytes |
content |
string |
— | File content (may be base64 encoded) |
contentEncoding |
?string |
null |
Content encoding type |
ValidateRequest¶
Request body for POST /asyncapi/validate
| Field | Type | Default | Description |
|---|---|---|---|
spec |
mixed |
— | Spec |
channel |
string |
— | Channel |
message |
string |
— | Message |
payload |
mixed |
— | Payload |
ValidationResponse¶
Response body for POST /asyncapi/validate
| Field | Type | Default | Description |
|---|---|---|---|
valid |
bool |
— | Valid |
errors |
array<string> |
— | Errors |
Enums¶
Method¶
HTTP method
| Value | Description |
|---|---|
Get |
Get |
Post |
Post |
Put |
Put |
Patch |
Patch |
Delete |
Delete |
Head |
Head |
Options |
Options |
Connect |
Connect |
Trace |
Trace |
LifecycleHookPhase¶
The five lifecycle phases a hook can be registered against.
Used to resolve a per-route named hook selection (LifecycleHooksConfig in
spikard-core::http) against the hooks actually registered on the server: a name is looked
up within one specific phase's registered hooks, not across all five, so a hook registered
for on_response can never be silently picked up by a route asking for on_request.
| Value | Description |
|---|---|
OnRequest |
On request |
PreValidation |
Pre validation |
PreHandler |
Pre handler |
OnResponse |
On response |
OnError |
On error |
SecuritySchemeInfo¶
Security scheme types
| Value | Description |
|---|---|
Http |
Http — Fields: scheme: string, bearerFormat: string |
ApiKey |
Api key — Fields: location: string, name: string |
SnapshotError¶
Possible errors while converting an Axum response into a snapshot.
| Value | Description |
|---|---|
InvalidHeader |
Response header could not be decoded to UTF-8. — Fields: 0: string |
Decompression |
Body decompression failed. — Fields: 0: string |
WebSocketMessage¶
A WebSocket message that can be text or binary.
| Value | Description |
|---|---|
Text |
A text message. — Fields: 0: string |
Binary |
A binary message. — Fields: 0: string |
Close |
A close message with a numeric close code (RFC 6455) and optional reason text. Common codes: 1000 Normal Closure, 1001 Going Away, 1005 No Status Received, 1006 Abnormal Closure. — Fields: code: int, reason: string |
Ping |
A ping message. — Fields: 0: string |
Pong |
A pong message. — Fields: 0: string |
Errors¶
AppError¶
Error type for application builder operations.
| Variant | Description |
|---|---|
Route |
Route registration failed. |
Server |
Server/router construction failed. |
Decode |
Failed to extract DTO from the request context. |
GraphQl |
GraphQL route registration failed (e.g. an unrecognized schema_type). |
GraphQlError¶
Errors that can occur during GraphQL operations
These errors are compatible with async-graphql error handling and can be converted to structured HTTP responses matching the project's error fixtures.
| Variant | Description |
|---|---|
ExecutionError |
Error during schema execution Occurs when the GraphQL executor encounters a runtime error during query execution. |
SchemaBuildError |
Error during schema building Occurs when schema construction fails due to invalid definitions or conflicts. |
RequestHandlingError |
Error during request handling Occurs when the HTTP request cannot be properly handled or parsed. |
SerializationError |
Serialization error Occurs during JSON serialization/deserialization of GraphQL values. |
JsonError |
JSON parsing error Occurs when JSON input cannot be parsed. |
ValidationError |
GraphQL validation error Occurs when a GraphQL query fails schema validation. |
ParseError |
GraphQL parse error Occurs when the GraphQL query string cannot be parsed. |
AuthenticationError |
Authentication error Occurs when request authentication fails. |
AuthorizationError |
Authorization error Occurs when user lacks required permissions. |
NotFound |
Not found error Occurs when a requested resource is not found. |
RateLimitExceeded |
Rate limit error Occurs when rate limit is exceeded. |
InvalidInput |
Invalid input error with validation details Occurs during input validation with detailed error information. |
ComplexityLimitExceeded |
Query complexity limit exceeded Occurs when a GraphQL query exceeds the configured complexity limit. |
DepthLimitExceeded |
Query depth limit exceeded Occurs when a GraphQL query exceeds the configured depth limit. |
IntrospectionDisabled |
Introspection query rejected because introspection is disabled Occurs when a query selects __schema or __type while the schema was configured with introspection disabled. |
InternalError |
Internal server error Occurs when an unexpected internal error happens. |
SchemaError¶
Error type for schema building operations
| Variant | Description |
|---|---|
BuildingFailed |
Generic schema building error |
ValidationError |
Configuration validation error |
ComplexityLimitExceeded |
Complexity limit exceeded |
DepthLimitExceeded |
Depth limit exceeded |