# wait_for_setup

> Wait for the services of a paid order to finish being set up, so the next step (set up email, install WordPress, point a domain) can follow at once.

- Tier: R
- Required scope: read:orders
- Annotations: readOnlyHint, idempotentHint
- Docs: https://api.inleed.com/tools/wait-for-setup

## Description

Wait for the services of a paid order to finish being set up, so the next step (set up email, install WordPress, point a domain) can follow at once. Use right after a payment receipt says the order is paid and services are being set up ("provisioning"). Polls the order for up to `max_wait_seconds` (default 40) and returns `{orderId, status, waitedSeconds, services[{serviceId, type, domain, status, provisioned, blockedOn}], verificationUrl, message}`. `status` is `ready` (all set up — continue), `configuring` (still working — call this tool again, at most three times in a row), `action_required` (a.se/.nu domain waits for the customer's BankID verification; the card shows the verification button — say so and stop waiting), `failed` (setup failed on our side; support is notified) or `manual` (staff set it up by hand; the customer is notified).

## Input schema

- `order_id` — integer (required). The order to wait for — from the payment receipt (orderId), create_order or list_orders.
- `max_wait_seconds` — integer. How long this call may wait before reporting back, in seconds (default 40; anything above 45 is clamped to 45 — call again for longer waits). Leave the default.

## Example call

```json
{
  "name": "wait_for_setup",
  "arguments": {
    "order_id": 1
  }
}
```