HodgefHodgef
  • Home
  • Blog
  • Projects
    • Apiker
    • PRSS Site Creator
    • simple-keyboard
Apiker
  • Getting Started
    • Project Structure
    • Deployment
  • Core Concepts
    • Configuration
    • Routes
    • Request
    • Response
    • State
    • Middleware
    • Validation
    • Scheduled Jobs
  • Features
    • Auth
    • Rate Limiting
    • Bans
    • Firewall
    • Logging
    • Beacons
    • Email
    • Geolocation
    • Timings
    • Admin Panel
  • Questions & Answers
    • Do I need a paid Cloudflare plan?
    • How do I run my API locally?
    • How do I protect a route?
    • How do I store data per user?
    • Why is every request returning 401?
    • How do I safely expose the admin panel?

Everything below is optional. Each feature is either switched on with an option in apiker.init, or used directly by importing its helpers — and each one stores its data in a Durable Object you list in objects.

Auth
Accounts, JWTs, email verification and password reset.
Rate Limiting
Cap how often a caller can hit a route.
Bans
Block an individual user or address.
Firewall
Push abusive IPs out to the Cloudflare edge.
Logging
Record events, with retention and pruning handled.
Beacons
Server-side analytics without a third party.
Email
Transactional email and the built-in templates.
Geolocation
Where a request came from.
Timings
Measure how long the work took.
Admin Panel
A dashboard for users, bans, logs and analytics.
PRSS Site Creator: Desktop blogging with AI, for free. Learn more →

Support development of this library:

Privacy PolicyTerms of Use
Built with PRSS
On this page