> ## Documentation Index > Fetch the complete documentation index at: https://bavlio.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Bulk From Dataset > Bulk find on an existing dataset (PR-E1 of 2026-05-22). Same money semantics as `/bulk` but the rows come from a server-resolved dataset (via shared eligibility predicate) instead of the client's request body. The frontend's Existing Datasets picker hits this route after a user confirms the spend in the modal. See `docs/plans/2026-05-22-bulk-find-email-existing-datasets-picker-plan.md` "Backend route shape" section for phase-by-phase ordering documentation, crash-safety properties, and failure-mode mapping. HTTP semantics: - 200 → job enqueued (or replayed from idempotency cache) - 400 → missing `Idempotency-Key` header - 402 → insufficient credits (with `required` + `available` in detail) - 404 → dataset not found OR not owned by user - 409 → `REQUEST_IN_FLIGHT` | `IDEMPOTENCY_KEY_REUSED_WITH_DIFFERENT_BODY` | `reconfirm_spend` (live `actual_estimated_credits` returned) - 422 → Pydantic validation OR `INELIGIBLE_SOURCE_TYPE` | `NO_ELIGIBLE_ROWS` | `DATASET_FETCH_FAILED` ## OpenAPI ````yaml https://api.bavlio.com/openapi.json post /api/v1/email-finder/bulk-from-dataset openapi: 3.1.0 info: title: Bavlio API description: >- Outreach automation API — lead enrichment, email campaigns, LinkedIn automation, and AI agent. Full docs at https://docs.bavlio.com. version: 1.0.0 x-guidance: product: Bavlio Data API protocols: - x402 description: >- Pay-per-call B2B data endpoints for AI agents. USDC on Base mainnet via x402 v2. See /openapi.json for pricing. Landing page + marketing details: https://bavlio.com/developers network: eip155:8453 docs_url: https://docs.bavlio.com x-payment-merchant-address: '0xcca4725e0e931982830bff523b141e1a7a58d3e7' servers: [] security: [] tags: - name: API Keys description: >- Create, list, and revoke API keys for programmatic access. JWT authentication required. - name: credits description: Credit balance, cost estimates, and transaction history. - name: campaigns description: Create, manage, launch, and monitor email campaigns. - name: campaign-personalization description: AI-powered email subject and body personalization for campaigns. - name: email-finder description: Find and verify email addresses for prospects. - name: sender-profiles description: Manage sender identity profiles for outreach. - name: sender-profile-chat description: Interactive chat for building sender profiles. - name: templates description: Email template CRUD. - name: suppression description: Do-not-contact suppression list management. - name: datasets description: Lead dataset listing, download, and updates. - name: user-extractions description: Uploaded lead file management and processing. - name: enrichment-chat description: Interactive chat for data enrichment sessions. - name: enrichment-processing description: Batch lead enrichment processing. - name: File Upload (CSV/Excel) description: Upload and preview CSV/Excel lead files. - name: connected-accounts description: LinkedIn account connections via Unipile. - name: linkedin-content description: LinkedIn post creation, scheduling, and management. - name: linkedin-playground description: Direct LinkedIn actions (profile lookup, messaging, engagement). - name: bavimail-proxy description: BaviMail domain, alias, and email management. - name: agent description: Bavi AI agent chat with SSE streaming. - name: notifications description: Notification preferences and delivery. - name: referral description: Referral code management and stats. - name: feedback description: User feedback submission. - name: authentication description: JWT token verification and user info. - name: users description: User quota and usage information. - name: Health description: Health checks and system status. - name: Personalization description: Core lead personalization engine. - name: Session Management description: Enrichment session lifecycle. - name: Session Processing description: Session data processing. - name: webhooks description: Inbound webhook handlers (Stripe, BaviMail, Unipile). paths: /api/v1/email-finder/bulk-from-dataset: post: tags: - email-finder summary: Bulk From Dataset description: >- Bulk find on an existing dataset (PR-E1 of 2026-05-22). Same money semantics as `/bulk` but the rows come from a server-resolved dataset (via shared eligibility predicate) instead of the client's request body. The frontend's Existing Datasets picker hits this route after a user confirms the spend in the modal. See `docs/plans/2026-05-22-bulk-find-email-existing-datasets-picker-plan.md` "Backend route shape" section for phase-by-phase ordering documentation, crash-safety properties, and failure-mode mapping. HTTP semantics: - 200 → job enqueued (or replayed from idempotency cache) - 400 → missing `Idempotency-Key` header - 402 → insufficient credits (with `required` + `available` in detail) - 404 → dataset not found OR not owned by user - 409 → `REQUEST_IN_FLIGHT` | `IDEMPOTENCY_KEY_REUSED_WITH_DIFFERENT_BODY` | `reconfirm_spend` (live `actual_estimated_credits` returned) - 422 → Pydantic validation OR `INELIGIBLE_SOURCE_TYPE` | `NO_ELIGIBLE_ROWS` | `DATASET_FETCH_FAILED` operationId: bulk_from_dataset_api_v1_email_finder_bulk_from_dataset_post parameters: - name: Idempotency-Key in: header required: false schema: anyOf: - type: string - type: 'null' title: Idempotency-Key requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/BulkFromDatasetRequest' responses: '200': description: Successful Response content: application/json: schema: {} '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - HTTPBearer: [] components: schemas: BulkFromDatasetRequest: properties: dataset_id: type: string format: uuid title: Dataset Id description: Dataset UUID owned by the authenticated user client_estimated_credits: type: integer exclusiveMinimum: 0 title: Client Estimated Credits description: User-confirmed estimate from the modal. Must be > 0. find_on_invalid: type: boolean title: Find On Invalid default: true type: object required: - dataset_id - client_estimated_credits title: BulkFromDatasetRequest description: >- Request body for /bulk-from-dataset. Fields: - `dataset_id`: target dataset UUID (must be owned by the authenticated user AND have an eligible `source_type`). - `client_estimated_credits`: REQUIRED. The estimate the user agreed to when they confirmed the spend in the modal. Server tolerance gate fires if `3 * len(eligible_rows) > 1.2 * client_estimated_credits`, returning 409 with `actual_estimated_credits` so the frontend can re-display the modal with the live number. HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: HTTPBearer: type: http scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.