The sandbox itself

Push notifications

So a finished turn can reach you when the tab is closed

On this page(4 sections)

What a device needs to subscribe
Send notifications to this device
Stop notifying a device
Send a test notification

What a device needs in order to subscribe, subscribing and unsubscribing, and a test. The test earns its place because there are four separate places a notification can be lost that nobody can inspect from outside.

GET/push/configWhat a device needs to subscribe

The public key and settings a browser or app needs before it can register for notifications from this sandbox.

What you send

Field	Type	Where
`id`Which device is asking	string	query

What comes back

Field	Type
`publicKey`The key a browser needs in…	string
`subscribed`Whether the asking device is already…	boolean

Try itanswered in this tab

curl

curl "$SANDBOX/push/config" \
  -H "x-intentic-control: $INTENTIC_TOKEN"

TypeScript

import { sandbox } from "@intentic/sandbox-client";

const result = await sandbox.push.config();

POST/push/subscribeSend notifications to this device

Registers one device. The sandbox only interrupts you on the three moments where attention is genuinely wanted: a turn has finished, the agent is stuck on a question, and something is waiting for approval.

What you send

Field	Type	Where
`when kind is "webpush"`	shape	body
`endpoint`requiredWhere that browser's push service accepts…	string	body
`keys`requiredWhat the browser handed you when…	object	body
`p256dh`requiredThe browser's public key, for encrypting…	string	body
`auth`requiredThe browser's secret, for the same	string	body
`when kind is "relay"`	shape	body
`url`requiredWhere to post a send	string	body
`deviceId`requiredThe device's id, which also identifies…	string	body
`secret`requiredProof that this sandbox may notify…	string	body

What comes back

Field	Type
`ok`Always true	true

Try itanswered in this tab

curl

curl -X POST "$SANDBOX/push/subscribe" \
  -H "x-intentic-control: $INTENTIC_TOKEN" \
  -H "content-type: application/json" \
  -d '{"kind":"webpush","endpoint":"https://sandbox-a1b2c3d4e5f6.intentic.dev","keys":{"p256dh":"…","auth":"…"}}'

TypeScript

import { sandbox } from "@intentic/sandbox-client";

const result = await sandbox.push.subscribe({
  "kind": "webpush",
  "endpoint": "https://sandbox-a1b2c3d4e5f6.intentic.dev",
  "keys": {
    "p256dh": "…",
    "auth": "…"
  }
});

POST/push/unsubscribeStop notifying a device

Removes one registered device. Others keep receiving.

What you send

Field	Type	Where
`id`requiredWhich device: a browser's push address,…	string	body

What comes back

Field	Type
`ok`Always true	true

Try itanswered in this tab

curl

curl -X POST "$SANDBOX/push/unsubscribe" \
  -H "x-intentic-control: $INTENTIC_TOKEN" \
  -H "content-type: application/json" \
  -d '{"id":"a1b2c3d4"}'

TypeScript

import { sandbox } from "@intentic/sandbox-client";

const result = await sandbox.push.unsubscribe({
  "id": "a1b2c3d4"
});

POST/push/testSend a test notification

Proves the whole chain end to end. Worth having, because there are four separate places a notification can be lost that nobody can inspect from the outside: the device's permission, its registration, the sandbox's key, and the delivery service.

What you send

Nothing. Call it as it is.

What comes back

Field	Type
`delivered`How many devices actually accepted it	integer

Try itanswered in this tab

curl

curl -X POST "$SANDBOX/push/test" \
  -H "x-intentic-control: $INTENTIC_TOKEN"

TypeScript

import { sandbox } from "@intentic/sandbox-client";

const result = await sandbox.push.test();