---
title: "Price finding a sequence's missing work emails"
method: GET
path: "/sequences/{sequence_id}/missing-emails/estimate/"
tags: ["sequences", "mcp-searchable-tool"]
---

# Price finding a sequence's missing work emails

`GET /sequences/{sequence_id}/missing-emails/estimate/`

## Request

- Base URL: `https://api.getoneprofile.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.getoneprofile.ai/sequences/{sequence_id}/missing-emails/estimate/`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

How many contacts in a sequence's audience have no email yet, and what finding their work emails would cost, before anything runs. The contacts are the audience rows with no address in the email column that a Find work email lookup has not tried yet: the same count the launch check's `contacts_missing_email` finding carries. Free, and changes nothing. Quote `expected_credits`; `adds_column` says a Work email column would be added first. Refused with a sentence to relay when nobody is missing an email, when the table has no name and company columns to find one from, or when lookups are unavailable. find_missing_emails spends it.

## Path parameters

- `sequence_id` string, uuid, required

## Response `200`

Successful Response

- MissingEmailsEstimateReadSchema: What finding the audience's missing work emails would cover and cost, before it runs.
  - `adds_column` boolean, required: True when that column does not exist yet and finding adds it to the audience table first. Adding it costs nothing.
  - `balance_sufficient` boolean, required: Whether the workspace's available credits cover the most it could cost.
  - `column_name` string, required: The Find work email column the addresses land in, by its name on the table.
  - `estimated_credits` number, required: The most it could cost, in credits: every row priced in full.
  - `expected_credits` number, required: What it usually costs, in credits: each row is charged the price of the source that answered it, read from which sources usually answer. Quote it beside estimated_credits, never instead of it: up to estimated_credits, usually about this. When the two are equal the lookup has one price: then quote that one figure, without up to.
  - `rows` integer, required: Contacts it would look up: audience rows with no email that a Find work email lookup has not tried yet. The same number the launch check's `contacts_missing_email` finding carries in `count`.
  - `scope_too_large` boolean, required: True when more contacts are missing an email than one run may cover. Narrow the audience's view first; running is refused until then.

## Other responses

- `401`: Unauthorized
- `403`: Forbidden
- `404`: Sequence not found.
- `422`: Invalid request made to the API.
- `500`: Internal server error.
- `502`: Bad gateway error.
- `503`: Service unavailable.

---

[API](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile.md) · [All operations](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile/llms.txt) · [OpenAPI document](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile/revisions/4a6bd71e3f02?raw)