Island User Management API Guide

Auth method: Bearer token for the tenant-specific SCIM endpoint

Setup steps

1. Log in to the Island management console as an administrator.
2. Open the identity or provisioning section.
3. Generate or reveal the tenant-specific SCIM endpoint URL and bearer token.
4. Use that endpoint and token in your IdP's SCIM connector configuration.

Create user via SCIM

• Method: POST
• URL: {tenant-scim-endpoint}/Users
• Watch out for: The base SCIM endpoint is tenant-specific and must be retrieved from the Island management console.

Request example

POST /Users {"userName":"user@example.com","active":true}

Response example

{"id":"123","userName":"user@example.com","active":true}

Update or deactivate user via SCIM

• Method: PATCH
• URL: {tenant-scim-endpoint}/Users/{id}
• Watch out for: Treat supported attributes and PATCH behavior as tenant-specific until validated in your IdP test tenant.

Request example

PATCH /Users/123 {"Operations":[{"op":"Replace","path":"active","value":false}]}

Response example

{"id":"123","active":false}

• Rate limits: No public rate-limit policy is documented for Island's tenant-specific SCIM endpoint.

• Rate-limit headers: No

• Retry-After header: No

• Rate-limit notes: Treat rate limits as undocumented and validate behavior with Island support before running large syncs.

• Pagination method: offset

• Default page size: Not documented

• Max page size: Not documented

• Pagination pointer: startIndex / count

• Webhooks available: No

• Webhook notes: No publicly documented webhook support found in Island's official documentation.

• Alternative event strategy: Not documented

• SCIM available: Yes

• SCIM version: 2.0

• Plan required: Enterprise

• Endpoint: Not documented

• Supported operations: Create User, Update User, Deactivate User

Limitations:

• SCIM endpoint URL is provisioned per-tenant and not publicly documented; must be obtained from Island admin console or support.
• Detailed supported operations, attribute mappings, and group provisioning capabilities are not publicly documented.
• Requires Enterprise plan (custom pricing, starting ~$25,000/year per pricing seed data).
• No public IdP-specific integration guides (Okta, Entra, Google Workspace, OneLogin) found in publicly accessible documentation.

The primary supported automation scenario is IdP-driven SCIM provisioning (e.g., Okta, Entra ID, Google Workspace, OneLogin).

The integration pattern follows standard SCIM 2.0 flows: generate a bearer token and tenant SCIM endpoint in the Island admin console, configure the IdP connector with those credentials, map attributes, and validate with a test user assignment.

However, IdP-specific integration guides are not publicly documented, and attribute mapping details must be sourced from the Island admin console directly.

For teams building identity graph automation or lifecycle orchestration, the absence of public pagination specs, rate limit headers, and webhook events means every integration assumption must be validated with Island support before production deployment.

Provision users via SCIM from an IdP

1. Log in to the Island management console with an admin account.
2. Navigate to the Identity/Provisioning section to generate a SCIM bearer token and obtain the tenant-specific SCIM endpoint URL.
3. Configure your IdP (e.g., Okta, Entra ID) with the Island SCIM endpoint URL and bearer token.
4. Map IdP user attributes to Island SCIM attributes as documented in the Island admin console.
5. Test provisioning by assigning a user in the IdP and verifying the user appears in Island.

Watch out for: The SCIM endpoint URL and token are tenant-specific and not publicly documented; they must be retrieved from the Island admin console. Contact Island support if the provisioning section is not visible, as it may require Enterprise plan activation.

The primary integration risk is documentation opacity: Island publishes no public API reference, no rate limit or pagination documentation, and no webhook events. Developers cannot pre-validate endpoint behavior, error response shapes, or attribute mapping coverage without live console access - which requires an active Enterprise contract.

SCIM group provisioning capabilities are not publicly documented, making it unsafe to assume standard SCIM group push behavior without explicit confirmation. Do not assume standard SCIM defaults for rate limits or pagination apply; treat all undocumented behavior as unconfirmed until verified directly with Island support.