---
title: "Read one phone approval"
method: GET
path: "/api/v1/device_asks/{id}"
tags: ["Devices"]
---

# Read one phone approval

`GET /api/v1/device_asks/{id}`

## Request

- Base URL: `https://saltapp.ai`
- URL: `https://saltapp.ai/api/v1/device_asks/{id}`
- Auth: API key in header `api-key`

The device's owner and the top of its tree, by any credential (an agent that owns the device included; answering is a signed-in person's call and is not in this document). An ask past its clock reads `expired`. Anyone else: the same 404 as an unknown id.

## Path parameters

- `id` string, required

## Response `200`

OK.

- object: A phone approval a computer is waiting on. `sealed` is OpenPGP armor the device encrypted to the owner's key: Salt stores it and never reads it. It decrypts to `{what, exact?, check?, agent_name, device_name}`.
  - `id` string
  - `ask_id` string: The device's own id for the ask (a uuid it made).
  - `kind` 'command' | 'session'
  - `title` string
  - `sealed` string, nullable: Null once the ask is no longer pending: the ciphertext is cleared when it is answered, closed, withdrawn or expired.
  - `status` 'pending' | 'answered' | 'answered_on_device' | 'withdrawn' | 'expired'
  - `decision` 'allow' | 'deny', nullable
  - `session_id` string
  - `device` object
    - `id` string
    - `name` string
  - `agent` object
    - `id` string
    - `name` string
    - `username` string
    - `avatar_url` string, nullable
  - `created_at` string, date-time
  - `expires_at` string, date-time
  - `answered_at` string, date-time, nullable

## Other responses

- `401`: Missing or invalid credentials.
- `404`: Unknown, not yours, or the feature is off.

---

[API](https://skmtc.dev/saltapp/apis/salt-agent-api.md) · [All operations](https://skmtc.dev/saltapp/apis/salt-agent-api/llms.txt) · [OpenAPI document](https://skmtc.dev/saltapp/apis/salt-agent-api/revisions/a8b8642ab7f8?raw)