Changelog

June 10, 2026

Summary

  • Added two endpoints for managing allowed IP address ranges in bulk: POST /organizations/{organizationId}/allowed-ip-address-ranges/bulk-create and POST /organizations/{organizationId}/allowed-ip-address-ranges/bulk-delete. Each request accepts up to 1,000 items and processes the batch atomically.

Added

  • Endpoints

    • POST /organizations/{organizationId}/allowed-ip-address-ranges/bulk-create: Create up to 1,000 allowed IP address ranges for an Organization in one request. The batch is created atomically: if any value fails validation or conflicts with an existing range, no ranges are created. The endpoint is not idempotent, so a retry after an unacknowledged 2xx response can return 409. On success, the endpoint returns the created ranges as an AllowedIpAddressRangesList. Requires the organization.allowedIpAddressRanges.create permission.
    • POST /organizations/{organizationId}/allowed-ip-address-ranges/bulk-delete: Delete up to 1,000 allowed IP address ranges for an Organization in one request. The batch is deleted atomically. Unknown and duplicate IDs are accepted and ignored, and matching ranges for the Organization are deleted. The endpoint returns 204 with no response body. Requires the organization.allowedIpAddressRanges.delete permission.

  • Schemas

    • BulkCreateAllowedIpAddressRangesRequest: Request body for bulk create. Required: allowedIpAddressRanges, a non-empty array of up to 1,000 CIDR-format strings.
    • BulkDeleteAllowedIpAddressRangesRequest: Request body for bulk delete. Required: allowedIpAddressRangeIds, a non-empty array of up to 1,000 allowed IP address range IDs.
    • AllowedIpAddressRangesList: Response body for bulk create. Required: allowedIpAddressRanges, an array of AllowedIpAddressRange.