Fiber guide · Go SDK

Fiber rate limiting,per customer, not per process.

One app.Use() checks each caller’s key, charges their credits, and applies their plan’s rate limit — shared across every Fiber instance you run.

Start building freeGo SDK docs
  • Keys issued per customer
  • Credits that refill
  • Limits per plan, not per process

Official SDKs with drop-in middleware for the stack you already run

  • Python
  • Node.js
  • Go
  • Rust
  • PHP
  • .NET
  • Java
API requests validated
100M+
Average key validation
<5ms
Average analytics ingest
<5ms
Check and log, end to end
<10ms

The usual Fiber rate limiter counts requests. It doesn’t know your customers.

Fiber’s limiter counts requests per KeyGenerator value over an Expiration window, in memory unless you plug in a storage driver.

With Fiber’s limiter middlewaretoday
// main.go — Fiber’s limiterapp.Use(limiter.New(limiter.Config{
	Max:        20,
	Expiration: 30 * time.Second,
	KeyGenerator: func(c fiber.Ctx) string {
		return c.Get("x-api-key")
	},
}))
  • Counters live in process memory — every worker and every instance keeps its own count
  • A storage driver to add before replicas agree
  • The header value is counted, never validated
  • No API keys: issuing, hashing, scoping, and revoking them is still yours to build
  • No credit balance: a request can’t cost 5 on one route and 1 on another, or refill each month
  • One limit for everyone — no per-plan limits for Free, Pro, and Enterprise customers
With ReqKey in Fiberone middleware
  • API keys issued per customer, prefixed, hashed, and revocable from the dashboard
  • A credit balance per customer — price each route, refill every hour, day, week, or month
  • Rate limits set per plan, shared by all of a customer’s keys, from 1 second to 24 hours
  • The same count on every worker, instance, and region — no Redis to run
  • Over the limit? A 429 with Retry-After, and no credits charged
  • Every request logged per customer — status, latency, endpoint — in under 5ms
Handlers read the verdict with c.Locals(reqkey.ContextDecisionKey). See the code

Fiber in three steps, one of them code.

ReqKey runs inside your API, not in front of it. Your server asks one question per request and gets an answer in under 5ms.

  1. 1

    Install the SDK

    go get github.com/Req-Key/reqkey-go@latest github.com/gofiber/fiber/v3

  2. 2

    Set your project key

    Copy it from the dashboard into REQKEY_PROJECT_KEY. It stays on your server.

  3. 3

    Add the Fiber middleware

    Every request is checked, charged, and logged before your handler runs.

main.gogo get github.com/Req-Key/reqkey-go@latest github.com/gofiber/fiber/v3
package main
 
import (
	"log"
	"os"
 
	"github.com/Req-Key/reqkey-go"
	reqkeyfiber "github.com/Req-Key/reqkey-go/fiber"
	"github.com/gofiber/fiber/v3"
)
 
func main() {
	app := fiber.New()
 
	app.Use(reqkeyfiber.MustMiddleware(reqkey.MiddlewareOptions{
		ProjectKey: os.Getenv("REQKEY_PROJECT_KEY"),
		APIID:      "api_payments",
		Mode:       reqkey.ModeBoth,
		KeyName:    "X-Startup-Key",
	}))
 
	app.Get("/protected", func(c fiber.Ctx) error {
		decision := c.Locals(reqkey.ContextDecisionKey).(*reqkey.VerificationResult)
		return c.JSON(fiber.Map{"request_id": decision.RequestID})
	})
 
	log.Fatal(app.Listen(":8080"))
}
Also in Go: net/http, Gin, Echo, ChiFull Go reference

Every request gets one of these answers

  • 200Valid key, credits charged — your handler runs
  • 402Out of credits
  • 403Key disabled, or not allowed on this API
  • 429Over the rate limit — no credits charged

Where ReqKey sits

Your customer
Your APIReqKey, under 5ms
Your handler

Responses go straight back to your customer. ReqKey sees the key check and the log line, nothing else.

Credits

Charge each route what it costs you.

A lookup can cost 1 credit and a render 5, from the same balance. Excluded paths are never validated, charged, or recorded. In Go:

Per-route credits · Go
// Exact paths or trailing-* prefixes: never validated, charged, or recorded
ExcludePaths: []string{"/health", "/openapi.json", "/docs/*", "/cron/*"},
 
// Or decide per request with a resolver
ShouldProtect: func(ctx context.Context, request *reqkey.MiddlewareRequest) (bool, error) {
	return strings.HasPrefix(request.Path, "/api/"), nil
},
 
// Charge different endpoints differently (non-negative integers)
CreditsResolver: func(ctx context.Context, request *reqkey.MiddlewareRequest) (int, error) {
	if request.Method == http.MethodPost {
		return 5, nil
	}
	return 1, nil
},

Rate limits

Set limits on plans, not in code.

Your Fiber code never hard-codes a number. Each plan carries its credits, refill, and rate limit; moving a customer to Pro changes all three with no deploy.

PlanCreditsRate limit
Free1,000 / month5 req / s
Pro50,000 / month50 req / s
Scale1,000,000 / month500 req / s
429Over the limit, a call is answered with Retry-After and costs nothing — no credits and no quota.

Example plans. You name them and pick the numbers.

Notes for Fiber teams hit in production.

Fiber v3

The adapter targets github.com/gofiber/fiber/v3 and is added with app.Use like any Fiber handler.

fasthttp speed

A check averages under 5ms, so it doesn’t undo the reason you picked Fiber.

Same options as the other Go adapters

Mode, key location, excluded paths, credits resolver, and failure mode are shared with net/http, Gin, and Echo.

Fiber rate limiting: the questions teams ask.

Something else? Ask the team or read the docs.

  • For keyed customer traffic, yes — ReqKey applies each customer’s plan limit. Keep Fiber’s limiter for anonymous routes if you like.

  • A JSON error with a stable code — invalid_api_key, insufficient_credits, access_denied, or rate_limited — and the matching status.

  • On their plan or on the customer (consumer) in ReqKey — a number of requests per window from 1 second to 24 hours, shared by all of that customer’s keys. Your Fiber code never hard-codes a limit, so upgrading a customer is a dashboard change, not a deploy.

  • A check averages under 5ms. ReqKey runs inside your app as middleware, not as a gateway in front of it, so responses go straight back to your customer.

  • You choose: fail closed and answer 503, or fail open and let requests through. Invalid keys are denied either way, and a validation is never retried, so no one is charged twice.

More Go guides.

Other languages

Ship API keys in Fiberin five minutes.

Free for your first 5 million requests every month. No card, no gateway, no rewrite.

Start building freeRead the docs