Skip to main content
Apivalk home page
Search...
⌘K
Releases
Getting started
Intro
Configuration
Contributing
Deprecation & Upgrade
Installation
Support Policy Release Cycle
Concepts
Coding Standards
Request Lifecycle
Structure
Best OpenAPI/REST Practices
HTTP
Overview
Controller
Request
Response
Routing
Routing
Route
Router
Rate Limit
Cache
Overview
Filesystem & Custom Cache
Middleware
Middleware
Request Validation
Sanitize
Authentication Middleware
Security Middleware
Rate Limit Middleware
Documentation (OpenAPI)
Overview
Docblock Generator
OpenAPI Generator
Property
Property Collection
Request
Response
Response Objects
Core System
Error Handling
Events
Util
Security
Overview
Identities
Scopes
Authenticators
Customization
Customization
Main page
Apivalk home page
Search...
⌘K
Main page
Main page
Search...
Navigation
Concepts
Best OpenAPI/REST Practices
Documentation
Documentation
Concepts
Best OpenAPI/REST Practices
Copy page
Apivalk follows and introduces modern best practices for OpenAPI
Copy page
TBD
Was this page helpful?
Yes
No
Previous
Overview
The HTTP layer in Apivalk provides a robust, type-safe, and structured way to handle the web request/response cycle. It bridges the gap between raw PHP superglobals and your business logic.
Next
⌘I