Skip to content

Collect Aetna Provider and Plan Data Through an API

Use one API call to retrieve public Aetna provider directories, plan summaries, formularies and benefit pages.

OUTPUT FORMATSHTMLJSONMarkdown

JavaScript rendering and residential proxy rotation are handled for you, so you can focus on the fields you need rather than browser and IP management.

Three common ways to use public Aetna data

Most teams need one of three things from public Aetna pages: a current provider network, a state-by-state plan comparison, or structured benefit and formulary details. Each maps to a different extraction checklist.

  • Provider network: doctors, specialties, locations and plan acceptance from the public directory.
  • Plan comparison by state: tiers, deductibles, in-network providers and formulary inclusions.
  • Plan detail analysis: plan name, premium, deductible, co-pay, network coverage and benefit summaries.

Decide which fields you need before you scrape. That choice determines whether rendered HTML is enough or whether you should request structured JSON directly.

How the workflow works

Aetna pages are JavaScript-heavy and sit behind anti-bot detection, so a plain HTTP fetch often returns an incomplete page. The workflow is designed to remove that friction:

  • Create an account and obtain an API key.
  • Call the API from your existing stack, or with cURL.
  • Send a GET request containing your key and an aetna.com URL for a provider directory, plan summary or other public page.
  • Add advanced parameters only when needed: render_js for JavaScript, stealth_proxy for CAPTCHA challenges, country_code for geo-targeting, and ai_extract_rules for natural-language extraction.

For structured output, map CSS selectors to field names with extract_rules, or describe the fields in natural language with ai_extract_rules. You can also request rendered HTML, clean Markdown, screenshots, or JavaScript scenarios for pages that need interaction before data appears.

Decision checklist before you scrape

Use this checklist to choose options and estimate cost before a large run:

  • Confirm the target is a public page: provider directory, plan summary, formulary or benefit page.
  • Enable JavaScript rendering when the directory or plan content loads dynamically.
  • Use premium proxy when standard routing is blocked; consider stealth proxy for CAPTCHA challenges.
  • Set country_code when results vary by country.
  • Choose extract_rules for stable, selector-based fields or ai_extract_rules for faster setup on changing layouts.
  • Space requests or use multiple sessions if the target throttles aggressive patterns.
  • Check the credit cost for the options you enabled, since rendering and proxy choices change the per-request cost.

This separates two common failure modes: missing data usually means rendering or extraction rules need adjustment, while blocks usually mean proxy or pacing needs adjustment.

Who it fits and what to expect

The service is positioned for data analysts, growth teams, developers and e-commerce businesses that need repeatable public-page data without maintaining headless browsers or proxy fleets. It states GDPR and CCPA compliance, noting that personal data from scraped sites is not collected or stored unless explicitly requested. Proxy rotation and headless rendering are intended to mimic real browsing and reduce IP-based blocking, with typical results described as taking 1-5 seconds.

Pricing and trial terms

Pricing for an Aetna scraping workflow depends on two things: the plan you choose and the options each request enables. Rather than quoting figures that may not apply here, treat this section as a worksheet you can fill in from current plan documentation before committing to a large run. The questions worth answering are: what monthly credit allowance and concurrency level does each plan include; how many credits does a single request consume when JavaScript rendering is on, when a premium proxy is used with rendering, and when a stealth proxy is required; whether unused credits carry over between billing periods; what the cancellation and refund terms are; and whether listed prices include or exclude VAT. A worked estimate helps: if a provider-directory page needs rendering plus a premium proxy, multiply that per-request credit cost by the number of pages in your crawl, then compare the total against the plan allowance. Keep the per-request cost assumptions and the plan figures side by side so a change in either is easy to spot. Confirm all commercial terms directly with the provider before purchase, since allowances, credit costs and tax treatment can change.

Frequently asked questions

Do I need an account to scrape Aetna?

No separate Aetna account is needed. You use the API key from your own account, send the public Aetna URL, and the service handles rendering and proxy rotation. The owner-confirmed trial allowance is recorded in the owner template below.

Can I scrape Aetna from a specific country?

Yes. Pass country_code to route the request through a residential IP in the chosen country, which helps when page content differs by location.

What is the rate limit for scraping Aetna?

Limits are based on plan concurrency rather than a fixed per-target rate. If Aetna throttles aggressive patterns, spacing requests or using multiple sessions can help.

How do I get structured JSON from Aetna?

Use extract_rules to map CSS selectors to field names, or ai_extract_rules with a natural-language specification. The response is returned as parsed JSON.

Which programming languages can I use to scrape Aetna?

Any language can call the API over HTTP. SDKs are described for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL also works.

How much does it cost to scrape Aetna?

Cost depends on the owner-confirmed plan and on options enabled per request. JS rendering, premium proxy and stealth proxy options carry different credit costs, recorded in the owner template below.