custom-endpoints

To add custom API endpoints to a Spiderly project, extend the generated base controllers with new methods or create fully custom controllers for specialized domain logic, then wire them into your DI container.

Yes, you can create webhook endpoints in Spiderly by building fully custom controllers that extend the generated base controllers, allowing you to handle specialized integrations and storefront scheduling patterns.

You reuse domain logic in custom Spiderly controllers by using dependency injection to inject custom services, ensuring consistent behavior while extending the generated CRUD patterns.

Custom Spiderly endpoints must follow Spiderly conventions by ensuring proper dependency injection wiring, applying appropriate authorization attributes, and aligning return types with the framework's standards.

You need custom non-CRUD endpoints in Spiderly when your application requires functionality beyond standard generated CRUD patterns, such as handling specialized storefront integrations or processing external webhook payloads.