---
title: "Approximately how many rows a search would return, and whether the CSV export tool would use your plan's remaining allowance."
method: GET
path: "/v1/me/export-estimate"
tags: ["meta"]
---

# Approximately how many rows a search would return, and whether the CSV export tool would use your plan's remaining allowance.

`GET /v1/me/export-estimate`

## Request

- Base URL: `https://api.jobopportunitiesapi.org`
- URL: `https://api.jobopportunitiesapi.org/v1/me/export-estimate`
- Auth: HTTP bearer

Accepts the same filters as GET /v1/jobs. Free to call: it never returns rows and consumes no record quota. estimated_rows is the query planner's approximation (EXPLAIN, no execution), not an exact count.

## Response `200`

estimated_rows, export_cap, would_use, remaining_this_month.

## Other responses

- `401`: Missing, unknown, revoked or expired key. All four are reported identically.
- `422`: A parameter we will not guess at: an unknown source_type or provider, an unparseable timestamp, a malformed cursor. Note the deliberate exceptions, which are clamps rather than errors: `limit` is capped at the plan maximum (a non-numeric value falls back to the default), and comma-separated lists are truncated to the per-parameter maximum shown on each. Unknown query parameters are ignored.
- `429`: Over your plan's per-minute or per-day limit. `Retry-After` says how long (seconds to the next minute boundary, or to UTC midnight on a daily breach). The body says exactly when the limit resets (`resets_at`, `resets_at_text`) and, when a higher plan exists, links a same-key upgrade (`upgrade_url`).

---

[API](https://skmtc.dev/jobopportunitiesapi/apis/job-opportunities-api.md) · [All operations](https://skmtc.dev/jobopportunitiesapi/apis/job-opportunities-api/llms.txt) · [OpenAPI document](https://skmtc.dev/jobopportunitiesapi/apis/job-opportunities-api/revisions/b5ef9709a0c9?raw)