Yahoo Email Account Creation

Request customer-owned Yahoo email accounts and retrieve successfully created account credentials through the run's OUTPUT record.

Pricing and access

Apify charges $2 per successfully created account, when the order has finished and you retrieve its credentials through the Actor. Failed creations are not charged. A partially successful order is charged only for the successful count. There is no paid start or dataset-item event.

No Find & Flip account, API key, or prepaid balance is required. Your verified Apify account owns the orders, and purchases are billed exclusively through Apify. Free-tier accounts can purchase using available Apify credit; the run spending limit must cover the requested purchase.

Set the Apify run spending limit to at least $2 x count before creating an order. For a later status/credentials run, allow enough to pay for any successful accounts not already paid. Check Apify Console's run pricing before starting.

Example

{
  "action": "create",
  "requestId": "yahoo-batch-001",
  "count": 1,
  "waitForCompletion": true,
  "maxWaitSeconds": 1800
}

Save the order UUID from OUTPUT. Reuse the same requestId and inputs if creation times out or the Actor restarts. A new ID creates a separate order. For a single account, you may supply both firstName and lastName; leave both blank for generated names. Bulk orders use generated names.

For later status or credential retrieval, copy the id returned in OUTPUT into orderId. Your custom requestId identifies a creation request; it is different from the generated order ID. You can also use list to find your order IDs.

{
  "action": "credentials",
  "orderId": "11111111-1111-4111-8111-111111111111",
  "waitForCompletion": false
}

Replace the example UUID with the actual id from your order. Supplying orderId during create does not assign an ID to the new order.

Actions

Action	Purpose
pricing	Read the standard Apify price and availability.
create	Queue 1-100 accounts using a stable requestId.
status	Poll an owned order and, once fulfilled or terminal, pay for successes and retrieve credentials.
credentials	Complete payment if needed and retrieve credentials from an owned order.
list	List your orders with limit (1-100) and offset.
cancel	Stop unfinished work. Already created accounts remain part of the order and can be retrieved through status/credentials.

waitForCompletion defaults to true and polls every ten seconds. maxWaitSeconds accepts 10-21600 seconds, default 1800. Account-creation availability, queue load, and provider responses affect completion time. Configure a compatible Apify run timeout with time for output export.

Creation defaults to eight parallel attempts even for one requested email. Once the requested quota is ready, spare attempts stop unless already requesting or waiting for SMS. Extra successful mailboxes become internal inventory and are never included in your bill or credentials. Fully fulfilled orders can be paid and retrieved immediately while protected spare flows finish in the background.

Stopping or timing out the Actor does not cancel the underlying order. Run status with its UUID to resume, or cancel to stop unfinished creation. Use the same Apify account for subsequent actions.

Output and payment recovery

Progress responses contain id, status, requestedCount, createdCount, and billing details. Once the requested quota is ready (or a partial order has ended) and payment is verified, OUTPUT includes an accounts array with each purchased account's ID, email, password, first name, and last name. Credentials are not written to the dataset or logs by this Actor.

Duplicate reads of a paid order do not create another purchase event. If a charge confirmation is lost, the service checks the saved payment claim against Apify's recorded event count. An uncertain claim may require support review instead of another charge. Keep the existing order ID rather than creating a replacement order.

Privacy and support

Generated credentials are sensitive. Keep inputs, OUTPUT records, and runs private, and change account passwords after retrieval when appropriate. Never select a real credential-bearing run as public sample output. The service retains provisioning and payment records to fulfill orders, attribute account ownership, and prevent duplicate charges. Your run token is used transiently for receipt verification and is not persisted by the backend.

Use the Actor's Issues tab for support with the run/order IDs only. Do not post API keys, email addresses, or passwords in public issues. This independent tool is not affiliated with, sponsored by, or endorsed by Yahoo. Use created accounts only for authorized purposes and in accordance with the provider's and Apify's terms. Creation does not guarantee future availability, acceptance, or account longevity.