Blame
|
1 | # Developer Overview |
||||||
| 2 | ||||||||
| 3 | This page is the starting point for developers building with AeThex. |
|||||||
| 4 | ||||||||
| 5 | AeThex developer work usually falls into one of four categories: |
|||||||
| 6 | ||||||||
| 7 | 1. Passport identity integration |
|||||||
| 8 | 2. Game or experience integration |
|||||||
| 9 | 3. Discord/community integration |
|||||||
| 10 | 4. Backend/API automation |
|||||||
| 11 | ||||||||
| 12 | --- |
|||||||
| 13 | ||||||||
| 14 | ## Common Developer Tasks |
|||||||
| 15 | ||||||||
| 16 | | Task | Read Next | |
|||||||
| 17 | |---|---| |
|||||||
| 18 | | Verify a Passport user | [[Authentication]] | |
|||||||
| 19 | | Connect a game | [[Game-Integration]] | |
|||||||
| 20 | | Use server APIs | [[API-Reference]] | |
|||||||
| 21 | | Add client tools | [[SDKs]] | |
|||||||
| 22 | | Receive events | [[Webhooks]] | |
|||||||
| 23 | | Connect Discord | [[Discord-Integration]] | |
|||||||
| 24 | | Debug an issue | [[Troubleshooting]] | |
|||||||
| 25 | ||||||||
| 26 | --- |
|||||||
| 27 | ||||||||
| 28 | ## Architecture Pattern |
|||||||
| 29 | ||||||||
| 30 | Most integrations use this pattern: |
|||||||
| 31 | ||||||||
| 32 | 1. Client requests identity/action. |
|||||||
| 33 | 2. Your server validates with AeThex. |
|||||||
| 34 | 3. AeThex returns scoped response. |
|||||||
| 35 | 4. Your app stores local state as needed. |
|||||||
| 36 | 5. Events are synced through APIs or webhooks. |
|||||||
| 37 | ||||||||
| 38 | --- |
|||||||
| 39 | ||||||||
| 40 | ## Developer Safety |
|||||||
| 41 | ||||||||
| 42 | - Keep secrets server-side. |
|||||||
| 43 | - Avoid storing unnecessary user data. |
|||||||
| 44 | - Validate all callbacks. |
|||||||
| 45 | - Retry idempotently. |
|||||||
| 46 | - Monitor status and error codes. |
|||||||