Record a bulk-import wizard completion
/portal/v1/accounts/{accountSlug}/applications/{appSlug}/environments/{envSlug}/identities/bulk-import-eventsRecords a single audit entry summarizing a completed CSV bulk-import wizard run (mode of create or invite, plus total/succeeded/failed/skipped counts); the per-batch create/invite entries are emitted separately by the bulk endpoints themselves. Writes no entity rows and returns 204 No Content. Requires the identity.manage permission.
Authentication
AuthorizationJWT access token. Never send alongside X-API-Key: a request carrying both is refused.
env_identities.manageDeveloper ConsoleCreate, invite, edit, and remove identities and assign their roles. Granted through an administrator role in the Admin Workspace; a valid token without it is refused with 403.
production_identities.accessDeveloper ConsoleAccess identities in production Environments. Applies to users only, and only in an Environment marked production: its identities are real end users. API keys and identity principals are exempt.
Path Parameters
accountSlugstring Required The Account's slug. An unknown one answers 404.
appSlugstring Required The Application's slug within the Account.
envSlugstring Required The Environment's slug within the Application.
Request body
application/json
modeenum Required totalnumber Required Total rows the wizard processed (succeeded + failed).
succeedednumber Required failednumber Required skippednumber Optional Rows the admin explicitly skipped (deselected in the preview, or unsent after a cancel).
Responses
Bulk-import wizard fired its completion event. Surfaces a single audit-log entry summarising the wizard run (mode, totals) so admins can ask 'did anyone run a bulk import this week?' without correlating per-batch events.
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
Errors
When the request can't be completed, the response body includes a stable error code you can branch on, and a correlation_id (also sent as the X-Correlation-Id header). Quote the correlation id when you contact support: it identifies the exact request in Canopy's logs.
account.capability_requiredForbiddenThe signed-in user's administrator roles do not grant the capability this endpoint requires.
Ask an account administrator to grant a role carrying the capability named in the Authentication section, then retry.
environment.production_identities_forbiddenForbiddenThe Environment is marked production and the caller is a user without production identity access.
Manage these people in the Admin Workspace, or ask an administrator to grant the Production Support role, then retry.
curl -X POST "https://auth.canopy-io.com/portal/v1/accounts/value/applications/value/environments/value/identities/bulk-import-events" \ -H "Authorization: Bearer $CANOPY_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "mode": "create", "total": 0, "succeeded": 0, "failed": 0, "skipped": 0 }'
HTTP/1.1 204 Bulk-import wizard fired its completion event. Surfaces a single audit-log entry summarising the wizard run (mode, totals) so admins can ask 'did anyone run a bulk import this week?' without correlating per-batch events. (empty body)
Tell us how we can improve this guide.