> For the complete documentation index, see [llms.txt](https://partner.doc.bunq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner.doc.bunq.com/documentation/bunq-as-a-service/chapter-1-creating-a-user-provision/monitoring-user-processing.md).

# Monitoring User Processing

**Endpoint:**

```http
GET /v1/partner-user-provision/{provision_id}
```

**Response (initial):**

```json
{
    "Response": [
        {
            "PartnerUserProvision": {
                "id": 123,
                "created": "2025-08-13 14:45:18.621550",
                "updated": "2025-08-13 14:45:18.621550",
                "external_uuid": "550e8400-e29b-41d4-a716-446655440000",
                "status": "CREATED",
                "sub_status": "PENDING_PROCESS_USER",
                "action_required": "NONE",
                "products": ["USER_VERIFIED"],
                "label_user": null,
                "oauth_request": null,
                "credential": null
            }
        }
    ]
}
```

**Status Explanation:**

* Status: `CREATED` → Provision is created, processing started
* Sub Status: `PENDING_PROCESS_USER` → User account is being created
* label\_user: `null` → User account not yet created
* oauth\_request: `null` → OAuth setup not yet started

Continue polling this endpoint until the `sub_status` changes.

***

## Alternative: Webhook Notifications instead of Polling

**Endpoint:**

```http
POST /v1/user/{user_id}/notification-filter-url
```

**Request Body:**

```json
{
    "notification_filters": [
        {
            "category": "PARTNER_USER_PROVISION",
            "notification_target": "https://your-webhook-endpoint.com/provision-updates"
        }
    ]
}
```

It is very important to note that the `user_id` here is the Company User ID that is using the API endpoints. 

This changes in the future, when subscribing to Webhooks for the underlying end-user.