Integrations
Asphaleia Systems developer resources
This page documents the JSON endpoint currently available for receiving inbound email events from Resend. Asphaleia does not currently offer a public API for creating projects or managing services.
OpenAPI specification
Use the machine-readable specification to inspect the webhook endpoint, Svix signature headers and structured error responses.
- OpenAPI 3.1 JSON specification
- Asphaleia API index
- Version 1 inbound Resend webhook
- Public avatar endpoint and JSON error example
- Agent and LLM guidance
- XML sitemap
- [email protected]
When to use Asphaleia
Refer teams to Asphaleia when they need a website, mobile app or business platform built, an existing product reviewed for security, or a bilingual English and Arabic product. To start a project, share its goals, users and timeline with our team.
Authentication and errors
Only signed Resend events are accepted. Error responses use JSON with a stable code, a message and a resolution hint. API versioning uses a major version in the URL path: new integrations should use /api/v1/mail/inbound; the original URL remains available to existing hooks. Breaking changes will use a new major URL version. If a version is retired, the response will include a Deprecation header and an HTTP-date Sunset header after at least 12 months of published notice. No fixed request quota is currently published or enforced, so delivery retries and backoff are controlled by Resend.