# Flowg8 · Retry provisioning

Retry a pending invitation after a technical failure.

Returns the existing invitation after successful provisioning, without resetting an existing account password. It retries pending provisioning; this is not a password-reset or renewal endpoint. No new person is created.

Service accounts require users:invite and can list/retry only invitations created by that same service account, including after key rotation. They cannot create admin invitations, assign approval groups or delegate credentials. Live invitations create real accounts; Sandbox invitations simulate provisioning and acceptance without sending emails.

## POST /v1/organization/invitations/{invitationId}/retry

Authentication: restricted integration key (scope: users:invite) or Flowg8 sign-in access token
Required tenant header: X-Organization-Id.
Required user permissions: Administrator or Sandbox developer required. The API checks current membership, roles, key scopes and resource permissions on every request. Documentation visibility grants no access.

## Request example (replace example IDs)

```sh
curl -X POST "https://api.flowg8.io/v1/organization/invitations/invitationId/retry" \
  -H "authorization: Bearer $FLOWG8_API_KEY" \
  -H "x-organization-id: 10000000-0000-4000-8000-000000000001" \
  -H "content-type: application/json" \
  --data-raw '{}'
```

## Response excerpt

```json
{
  "status": "invited"
}
```

Source: /docs/retry-invitation
Full schemas: /docs/openapi.json