Developer Overview
This page is the starting point for developers building with AeThex.
AeThex developer work usually falls into one of four categories:
- Passport identity integration
- Game or experience integration
- Discord/community integration
- Backend/API automation
Common Developer Tasks
| Task | Read Next |
|---|---|
| Verify a Passport user | Authentication |
| Connect a game | Game-Integration |
| Use server APIs | API-Reference |
| Add client tools | SDKs |
| Receive events | Webhooks |
| Connect Discord | Discord-Integration |
| Debug an issue | Troubleshooting |
Architecture Pattern
Most integrations use this pattern:
- Client requests identity/action.
- Your server validates with AeThex.
- AeThex returns scoped response.
- Your app stores local state as needed.
- Events are synced through APIs or webhooks.
Developer Safety
- Keep secrets server-side.
- Avoid storing unnecessary user data.
- Validate all callbacks.
- Retry idempotently.
- Monitor status and error codes.