Managing Apps

In todoke, an “app” is the unit for managing Push notifications. You can create, view, and delete apps from the dashboard’s app list screen (/).

Creating an app

1. In the “新しいアプリを作成” (Create a new app) form at the bottom of the app list screen, enter the “アプリ名” (App name) (required field).
2. Click “作成” (Create). While creating, “作成中…” (Creating…) is displayed.

The created app is added to the list directly. If you have no apps yet, the list displays “アプリがありません。最初のアプリを作成してください。” (You have no apps. Please create your first app.)

Caution

On the Free plan you can create up to 1 app. If you try to create another app after reaching the limit, an error “フリープランではアプリを1つしか作成できません” (You can only create one app on the Free plan) (PLAN_LIMIT_EXCEEDED, HTTP 403) is displayed. Adding more apps requires a plan upgrade.

At the top of the app list screen, the current plan (Free / Pro) is shown, and on the Free plan a “Pro にアップグレード →” (Upgrade to Pro →) link is displayed. There are also usage bars for “今月の配信成功数” (Successful deliveries this month) and “購読者数” (Number of subscribers); when usage reaches 80% of the limit, a warning and an upgrade prompt appear. Failed deliveries do not count toward the monthly limit.

The app list and navigating to the detail screen

In the app list, each app is displayed as a card together with its app name and the leading part of its ID. Clicking a card takes you to that app’s detail screen (/apps/:id), where you can view statistics, the VAPID public key, and API keys. You can return to the list via the ”← アプリ一覧” (← App list) link in the detail screen’s header.

Sending to everyone

The “全員に送信” (Send to everyone) section on the app detail screen is the human-side fallback path when the agent stops. Enter a title, body, and optional destination URL to send a notification to every currently active subscriber.

1. Enter the “タイトル” (Title) and “本文” (Body). If the notification should open a destination when clicked, enter an https:// URL in “URL（任意）” (URL, optional).
2. Click “全員に送信” (Send to everyone).
3. Confirm that “アクティブ購読者 N 件に送信します” (Send to N active subscribers) shows the intended recipient count, then click “N 件に送信する” (Send to N subscribers). Click “キャンセル” (Cancel) to stop instead.
4. When “送信を受け付けました” (Send accepted) appears, the notification has been placed on the send queue. Check the “送信履歴” (Send history) section on the same screen for delivery results.

Caution

Sending is unavailable after the Free plan’s monthly limit is reached. The “全員に送信” (Send to everyone) button is also disabled when there are no active subscribers.

Webhooks and delivery logs

On the Pro plan, you can configure a Webhook URL in the “Webhook URL” section of the app detail screen. When you save the URL, the signing secret is displayed once. See the Webhook guide for configuration and signature-verification details.

While a Webhook URL is configured, the “配信ログ” (Delivery log) area in the same section shows the 10 most recent final-attempt results. Each row shows the date and time, success or failure, HTTP status, error category, and the first eight characters of the send_id. Timeout and network errors show - for the HTTP status and timeout or network_error for the error. Redirects are failures labeled redirect; other non-2xx responses are labeled http_<status>.

Delivery logs are retained according to the current plan: 7 days on Free and 90 days on Pro. If you downgrade from Pro to Free, the 7-day retention period applies from the next scheduled cleanup. Deleting the app or account cascade-deletes its delivery logs.

API key issue and deletion history

Open “発行・削除の履歴” (Issue and deletion history) in the “API キー” (API keys) section of an app’s detail screen to view the time, action, key name, scope, and operator for each API key issue or deletion. The history is fetched when you open it. If there are 21 or more events, select “さらに読み込む” (Load more) to view older events.

Actions performed from the Dashboard show “Dashboard” as the operator. Actions performed through MCP show the API key name used for the operation; if that operator key has since been deleted, “削除済みキー” (Deleted key) is shown. Deleting the key that an event describes does not remove the key name and scope snapshot stored in the history.

API key history is not subject to send-log retention or cron deletion and is retained while the app exists. Deleting the app or account cascade-deletes the history.

Deleting an app

Clicking the “アプリを削除” (Delete app) button to the right of the heading (app name) on the app detail screen switches to a confirmation display.

1. Clicking “アプリを削除” (Delete app) displays the confirmation message “元に戻せません。削除しますか？” (This cannot be undone. Delete?) along with two buttons, “削除する” (Delete) and “キャンセル” (Cancel).
2. Clicking “削除する” (Delete) executes the deletion. While executing, “削除中…” (Deleting…) is displayed. Clicking “キャンセル” (Cancel) aborts the deletion.

Danger

When you delete an app, the API keys, API key history, subscribers, statistics, send logs, and Webhook delivery logs associated with that app are all cascade-deleted and cannot be restored. Before deleting, make sure you have any data you need (such as a copy of issued API keys).