basic-httpapi

Basic httpapi example

Legacy-style net/http handlers wrapped with httpapi to auto-generate OpenAPI and JS/TS/PY clients. Use this pattern when you must keep an existing route shape while migrating toward RPC.

Run

go run .

Docs/clients: http://localhost:8000/api/docs/

Try it

curl http://localhost:8000/api/v1/lookup/states/

curl http://localhost:8000/api/v1/lookup/states/mn

curl 'http://localhost:8000/api/v1/lookup/states/mn?verbose=true'

curl http://localhost:8000/api/v1/secure/states/mn \
  -H 'Authorization: Bearer demo-token'

curl http://localhost:8000/api/v1/secure/states/mn \
  -H 'X-API-Key: demo-api-key'

curl -X POST http://localhost:8000/api/v1/lookup/states \
  -H 'Content-Type: application/json' \
  -d '{"code":"ca","name":"California"}'

curl -X POST http://localhost:8000/api/v1/compliance/facebook \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'hub.mode=subscribe' \
  --data-urlencode 'hub.verify_token=demo'

Extend it

• Add a new handler with httpapi.WrapFunc to mirror a real legacy endpoint you plan to migrate.
• Introduce request/response structs that match your production payloads, then observe the OpenAPI change.
• Use path/query tags to preserve scalar parameter types in OpenAPI and generated clients.
• Use httpapi.AuthAny(...) when a route accepts one of several auth schemes.
• Use httpapi.FormBody(...) for form-urlencoded callbacks.
• If you are ready to migrate, port one route to RPC and compare the generated clients.