# [Feature Request] Teams OpenAPI: Add clientIp / deviceId to usage-events
**Category:** Feature Requests / Teams OpenAPI / Enterprise Governance
-–
## Problem
Our organization uses Qoder Teams with **shared member accounts** (one seat used by multiple people, sometimes from both intranet and public network). We are building automated monitoring on top of the Teams OpenAPI.
The current `GET /v1/organizations/{org_id}/usage-events` response only includes:
`timestamp`, `userId`, `userEmail`, `source`, `operation`, `modelTier`, `credits`, `cost`
There is **no client IP, device identifier, or session fingerprint**. As a result, we cannot:
1. Estimate how many distinct users are behind one member account
2. Distinguish intranet vs. public-network access for compliance
3. Attribute usage or detect abuse on shared accounts
4. Close the governance loop for Enterprise customers using OpenAPI automation
We already use the API for quota monitoring, seat-month balance tracking, and self-service quota adjustment. The missing client metadata is the main gap.
**Docs:** Usage APIs - Qoder
-–
## Proposed Solution
Add optional metadata fields to each `usage-events` record (member-level and org-level):
| Field | Type | Description |
|-------|------|-------------|
| `clientIp` | string | Request source IP (masking last octet is acceptable, e.g. `10.1.2.xxx`) |
| `clientNetwork` | string | Optional label: `intranet` / `public` |
| `deviceId` | string | Optional hashed device fingerprint (not raw hardware IDs) |
| `sessionId` | string | Optional client session ID for grouping requests by actual user |
This is **metadata only** — no prompts, code, or terminal output. Similar in spirit to Enterprise Audit Log’s `MemberLogin` traceability.
-–
## Use Cases
- **Shared account detection:** multiple distinct `clientIp` values in a short window → alert
- **Compliance:** public IP on an intranet-only account → security alert
- **Cost attribution:** aggregate credits by IP/device for internal chargeback
- **OpenAPI automation:** feed enriched events into dashboards and data warehouses
-–
## Priority
**Medium — Important improvement**
Not blocking core usage, but valuable for Enterprise account governance, security audit, and cost management. We are an active Teams customer using redemption-code billing and OpenAPI integration.
-–
## Environment
- Organization purchased via third-party redemption codes (Aliyun CN)
- Integrating via Teams OpenAPI with scheduled quota sync
- Also requesting via our official DingTalk support channel
Thank you for considering this!