AOGC REST API
Enterprise REST API for procurement and organization management. JWT authentication, role-based access control with Spatie Permissions, RFQ workflows with committee voting, and auto-generated API documentation via Scribe.
Procurement ran on spreadsheets and email — no centralized system, no audit trail, and no self-service documentation.
Backend and API engineer
- API architecture
- Identity and authorization
- Procurement workflows and documentation
How I approached it
I shaped the API around the organization and procurement workflows, using JWT authentication and role-based permissions for access, RFQ endpoints for committee review, and generated Scribe documentation for the consuming team.
Inside the engineering
Identity and permissions
JWT handles authentication, while Spatie Permissions provides role-based authorization across three business modules. These are separate parts of the access model: identifying the caller and controlling the actions available to their role.
Procurement as an API workflow
RFQ workflows and committee voting are part of the procurement API, alongside organization management. The implementation brings those business operations into defined endpoints rather than leaving the workflow entirely in spreadsheets and email.
Documentation for the consuming team
Scribe generates the API documentation, giving the consuming team a reference for the implemented endpoints. Documentation is part of the delivery scope alongside authentication, permissions, and procurement workflows.
- Full procurement system with RFQ workflows
- Role-based access across 3 business modules
- Self-documenting API for team onboarding
Public links are included when confidentiality permits. Delivery claims describe implemented scope; performance figures are shown only when they were measured for the project.
Need a system with similar scope?
I build full-stack systems end-to-end — architecture, code, deployment, and the operations behind it. If this kind of delivery matches what you need, let's talk.