| # Integration API Contracts Audit |
|
|
| We found the following Pydantic models in `backend/main.py`: |
|
|
| - **Alert**: Used for system notifications. |
| - **IssueCreate** / **IssuePatch**: For handling issues. |
| - **SOSPayload**: Triggered by guest/staff in emergencies with `lat`/`lng`. |
| - **GossipTrackingStart**: Related to tracking a person via the gossip network. |
| - **LoginPayload** / **RefreshPayload** / **LogoutPayload**: Auth mechanisms. |
| - **TrackingResetPayload**: To reset the session tracking. |
| - **ChatPayload**: For LLM/Chat interactions. |
|
|
| The contracts are clean and utilize standard types. Most use `Optional` extensively, offering flexibility but requiring robust `None` checking in downstream handlers. |
|
|
