# Domain connection examples

Set `APP_ORIGIN` to your existing app's returned HTTPS origin and `BEARER` to
its owner token in your trusted shell. Do not paste tokens into public prompts,
hosted files or screenshots. The clients print results, not credentials.

## Request the connection

```sh
node samples/domain-flow.mjs create www.example.com CNAME
# Or use A for returned A/AAAA address records, usually at the zone apex:
python3 samples/domain_flow.py create example.com A
```

These are separate names, so they receive separate bindings and TXT proofs.
Show the exact `verification` and `dns` records returned by the API. Ask the
user before changing conflicting existing DNS records. Keep the TXT proof.

## Verify and inspect

Replace `dom_RETURNED_ID` with the returned `bindingId`:

```sh
node samples/domain-flow.mjs verify dom_RETURNED_ID
python3 samples/domain_flow.py list
bash samples/domain-flow.sh list
```

Wait at least 30 seconds before another explicit verification. DNS updates
can take longer. Only `active` plus `tlsReady: true` means HTTPS is ready.
Until then, the original JMPKit link continues to work.

## Disconnect

```sh
bash samples/domain-flow.sh remove dom_RETURNED_ID
```

Confirm the user's intent first. This detaches the name, not the app or data.
Afterward the user can remove the corresponding DNS records.