Spikard FFI

C/C++ FFI bindings for the spikard HTTP framework. Stable ABI shared library for native integration, cross-language bridging (Go, Zig, Kotlin JNI), and embedding the Rust HTTP core into any C-compatible host.

What This Package Provides

• HTTP application core — typed routing, request data extraction, validation, lifecycle hooks, and Tower middleware from the Rust engine.
• Spec-driven work — OpenAPI, AsyncAPI, GraphQL SDL, JSON-RPC, and SQL-to-HTTP codegen are shared across bindings.
• Cross-language parity — generated bindings use the same DTOs, fixtures, and error model, so behavior does not drift between runtimes.
• Native integration — no sidecar server required; each package calls the Rust core through its language-native bridge.
• C ABI — stable shared library surface for custom hosts and secondary bindings.

Installation

cargo add spikard-ffi

System Requirements

• C99 or C++11 compiler; spikard-ffi static/shared library from GitHub Releases

Quick Start

See the spikard repository for usage examples and guides.

Features

• HTTP routing — type-safe route definitions with path, query, and body parameter validation
• OpenAPI / AsyncAPI / GraphQL / JSON-RPC — code generation and spec parsing built in
• Tower middleware — compression, rate limiting, timeouts, auth (JWT/API key), static files
• Lifecycle hooks — onRequest, preValidation, preHandler, onResponse, onError
• Fixture-driven testing — shared JSON fixtures drive tests across all language bindings
• Polyglot — single Rust core, thin bindings for Python, Node.js, Ruby, PHP, Elixir, Go, Java, C#, Kotlin, Dart, Gleam, WASM, Swift, Zig, and C FFI

Documentation

• Repository — source code, examples, and contributing guide
• Examples — working server examples
• Issues — bug reports and feature requests

Contributing

Contributions are welcome. See CONTRIBUTING.md.

License

MIT License — see LICENSE for details.