> ## Documentation Index > Fetch the complete documentation index at: https://docs.spenza.com/llms.txt > Use this file to discover all available pages before exploring further. # Update a user-group ## OpenAPI ````yaml /openapi.yaml put /api/v1.1/user-groups/{name} openapi: 3.1.0 info: title: Spenza Partner API version: 3.0.0 summary: >- Partner API for SIMs, eSIMs, plans, billing, users, groups and numbers — v1.1 surface. description: > The **Spenza Partner API** lets you manage SIMs, eSIMs, plans, subscriptions, billing, users, phone numbers, teams and device/SIM/user groups programmatically. All endpoints follow one consistent standard: - **Auth** — exchange your API `key` + `secret` for a bearer token, then send `Authorization: Bearer ` on every request. - **Envelopes** — success responses are `{ success, data, meta? }`; errors are `{ success: false, error: { code, message, details? } }`. - **Pagination** — list endpoints accept `page` (1-indexed) and `pageSize` (max 100); totals are returned in `meta`. - **Idempotency** — many write endpoints honor an optional `Idempotency-Key` request header so a retried call replays the original result instead of repeating the side effect. - **Async operations** — a handful of endpoints (eSIM provisioning, port-in, the `/api/v3/...` purchase variants, top-up) return `202` (`201` for top-up) with a `transactionId` + `statusEndpoint` instead of the finished resource. Poll `GET /api/v3/transactions/{transactionId}` (no auth required) until the transaction reaches a terminal status. One resource — **port-in submission** — is a documented exception: it lives at `POST /api/v3/port-in`, requires an Admin-tier account role rather than just a valid bearer token, and is **not** on the standard envelope (see that operation's description for its exact response shape). contact: name: Spenza API Support email: support@spenza.com url: https://spenza.com license: name: Proprietary url: https://spenza.com/terms x-logo: url: https://spenza.com/logo.png altText: Spenza servers: - url: https://api.spenza.com description: Production security: - bearerAuth: [] tags: - name: Authentication description: Exchange API credentials for a bearer token. - name: SIMs description: List, inspect, assign and manage SIMs. - name: Subscriptions description: Plan subscriptions attached to SIMs. - name: Plans & Catalog description: Purchasable plans and SIM products. - name: eSIM description: Provision eSIMs and fetch activation QR / install status. - name: Billing description: Invoices, credit balance and top-ups. - name: Users description: End users (employees) on your account that SIMs/devices are assigned to. - name: Orders & Transactions description: Order history and financial transactions. - name: Numbers & Port-in description: Check port-in eligibility and port existing numbers into Spenza. - name: Messaging description: Send outbound SMS from a provisioned number. - name: Webhooks description: Register endpoints for operator SMS/voice events and inspect deliveries. - name: Notifications description: In-account notifications and delivery preferences. - name: Device Groups description: Organize devices into named groups with spend/data limits. - name: SIM Groups description: Organize SIMs into named groups with spend/data limits. - name: User Groups description: Organize users (departments) into named groups with spend/data limits. - name: Devices description: The device catalog (phones/tablets) and their assignment to users. - name: Team Members description: Admins who manage your Spenza account (distinct from Users/end-users). - name: Async Status description: Universal status poll for any asynchronous (v3) operation. paths: /api/v1.1/user-groups/{name}: parameters: - name: name in: path required: true description: Exact match, case-sensitive. Not renamable. schema: type: string example: Engineering put: tags: - User Groups summary: Update a user-group operationId: updateUserGroup parameters: - $ref: '#/components/parameters/IdempotencyKey' requestBody: content: application/json: schema: type: object properties: spendLimit: type: number minimum: 0 dataQuota: type: number minimum: 0 currency: type: string maxLength: 10 dataUnit: type: string enum: - KB - MB - GB responses: '200': description: >- Updated. Note: the response is a client-side merge of the pre-update group snapshot with the raw fields you sent, not a fresh read of the row after saving — omitted fields echo the prior stored value, and fields you sent are echoed back as-submitted rather than re-read from the database. content: application/json: example: success: true data: name: Engineering spendLimit: 2500 dataQuota: 200 currency: USD dataUnit: GB '400': description: An invalid field value. content: application/json: example: success: false error: code: VALIDATION_ERROR message: One or more fields failed validation. details: validationErrors: - spendLimit must not be less than 0 '401': $ref: '#/components/responses/Unauthorized' '404': description: No user-group with that name. content: application/json: example: success: false error: code: USER_GROUP_NOT_FOUND message: >- We couldn't find a user-group with that name on your account. '409': description: >- The `Idempotency-Key` header was reused with a different request body/route, or reused while the original request was still in flight. content: application/json: examples: idempotencyKeyReused: value: success: false error: code: IDEMPOTENCY_KEY_REUSED message: >- This request was already submitted with different details — please use a new idempotency key. idempotencyKeyInFlight: value: success: false error: code: CONFLICT message: >- This request is already being processed — please retry in a moment. '429': $ref: '#/components/responses/RateLimited' components: parameters: IdempotencyKey: name: Idempotency-Key in: header required: false description: > Any string unique to this logical request. On a retry with the same key and the same request body, the original response is replayed verbatim (with an `Idempotency-Replayed: true` response header) instead of the action repeating. Reusing the key with a **different** body or on a different route returns `409 IDEMPOTENCY_KEY_REUSED`. A replay attempted while the original call is still in flight returns `409 CONFLICT`. Optional — omit it and the endpoint behaves exactly as it would otherwise. schema: type: string example: a1b2c3d4-idem-key-001 responses: Unauthorized: description: Missing, malformed or expired bearer token. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: success: false error: code: UNAUTHORIZED message: Missing or invalid token. RateLimited: description: > Rate limit exceeded for this endpoint (or the account-wide default of 120 req/min). Only `Retry-After` is present on this response — the `X-RateLimit-*` headers below are sent on successful (non-429) requests, not on the 429 itself. headers: Retry-After: description: Seconds until you can retry. schema: type: integer content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: success: false error: code: RATE_LIMITED message: 'ThrottlerException: Too Many Requests' schemas: ErrorEnvelope: type: object required: - success - error properties: success: type: boolean example: false error: type: object required: - code - message properties: code: type: string example: SIM_NOT_FOUND message: type: string example: We couldn't find a SIM with that ICCID on your account. details: description: >- Present on some 4xx errors (for example a list of missing fields). Always absent on 5xx. type: object securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: Bearer token obtained from `POST /api/v1.1/auth/token`. ````