API

1. Get an API key

There are two kinds of keys. Only API keys work for HTTP requests.

API keys are listed on the API page and link keys on the Links page. Generated keys start with dsk_ and are 36 characters long; a key you choose yourself on the API page (see Live URLs below) works the same way.

2. Send the request

curl -X POST https://programmable.info/api/sheet \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{"domains": ["stripe.com", "notion.so"], "columns": "company, tech stack", "format": "json"}'

In an automation tool, the same thing goes in its HTTP step:

Everywhere: method POST, URL https://programmable.info/api/sheet, your API key as the Bearer token, and a JSON body. To use data from an earlier step, put its field inside the body, e.g. {"domains": ["{{website}}"]}.

3. Read the rows

With "format": "json" you get one document back once every row is done:

{
    "rows": [
      { "domain": "stripe.com", "company_name": "Stripe", "industry": "Financial services", "cms": "Custom", ... },
      { "domain": "notion.so", "company_name": "Notion", ... }
    ],
    "summary": { "rows": 2, "ok": 2, "failed": 0, "skipped": 0, "credits_charged": 2, "seconds": 3.1, "ai_cost_usd": null },
    "errors": []
  }

Without format the response is a CSV that streams row by row (good for files and spreadsheets). Each row keeps your input columns, then the enrichment, and a row that couldn't be enriched says why in enrich_error.

The request waits for every row. Most tools allow a few minutes; for long lists, send "webhook": "on" and let your CRM webhook receive rows in batches as they finish.

Body fields

Send one of domains, people, linkedin or products. Everything else is optional.

Column groups: email (email finder), company (company), leadership (leadership), site (website), tech (tech stack), email_auth (email setup), dns (dns), security (security), socials (social profiles), contacts (contacts), domain_age (domain age), providers (your data providers), product (product), product_price (price & stock), product_ids (product ids), product_variants (variants), product_market (marketplaces), product_reviews (ratings), performance (performance & third parties), hiring (hiring), gtm (go-to-market), sitemap (site map), news (news & buzz), footprint (digital footprint), public_footprint (public footprint), trust (trust & compliance), filings (filings & public record), govcon (government contracting), commerce (store signals), google (google data), changes (changes over time).

Send a CSV file

Post the file as multipart form data. Columns are recognized from their contents, whatever they're called; correct a guess with map, and say has_header=no when the first row is data.

curl -X POST https://programmable.info/api/sheet \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -F file=@contacts.csv \
    -F "map=email:Contact Info|company:Employer" \
    -F format=json

Live URLs (GET)

For spreadsheets and browsers, the same options work as a URL: https://programmable.info/x/live?key=YOUR_KEY&domains=stripe.com,notion.so. In Google Sheets: =IMPORTDATA("https://programmable.info/x/live?key=…&domains=stripe.com"). A key in a URL can be seen by anyone who sees the URL, so make these on the Links page: their keys can be limited and locked to the link.

No key needed in a browser: open https://programmable.info/x/live?domains=stripe.com,notion.so&columns=company,tech and, if you're not signed in, you're asked to sign in (or create an account) and brought straight back, with the cost shown before it runs. Signed in, links you type or bookmark run at once; a link someone else sends you shows the cost and a Run button first, so nobody can spend your credits with a link. Tools like Google Sheets and Zapier have no browser session, so they still need key=. That key can be one we generate (dsk_…) or one you choose on the API page, like key=velvet-kayak-mango-orbit, so you can type links from memory; chosen keys must be hard to guess, and wrong keys are rate-limited.

Plain-English requests (request=)

Instead of naming every parameter, say what you want: https://programmable.info/x/live?request=find the CTOs at fintech startups in New York, with deep research on the AI tools they use (or the shorter q=). It's translated into the named parameters above on your own AI key, so you need Anthropic, OpenAI, Gemini or OpenRouter connected.

• Confirmed once. The first time, you see what the link will do (what it finds, the questions it asks your AI, anything it had to guess and the exact link with named parameters) and press Run. After that the translation is remembered for your account, so the same link runs the same way every time, also from Google Sheets or Zapier. Rewording it translates and asks again.
• Named parameters win. Mix both, e.g. request=deep research on their AI tools&domains=stripe.com,notion.so: anything the link spells out is used as is, and the request only fills in the rest.
• From automations an unconfirmed request returns 428 with a confirm link to open once in a browser. In Settings you can choose to confirm only requests that spend your money; those (AI questions, paid provider data, sending rows to another tool) are always confirmed once.
• Only the translation is kept, never the rows.

Google Sheets add-on

Formulas and a sidebar inside your own sheet. In Google Sheets open Extensions → Apps Script, then paste in Code.js (as Code.gs) and add an HTML file named Sidebar with Sidebar.html. Save, reload the sheet, and a Programmable menu appears. Open the sidebar and paste an API key.

• =PROGRAMMABLE(A2, "employees") one value about a company
• =PROGRAMMABLE_ROW(A2, "company, tech stack") several columns across the row, with =PROGRAMMABLE_HEADERS("company, tech stack") for the header
• =PROGRAMMABLE_EMAIL("Jane Doe", "acme.com") a work email
• Programmable → Enrich selection fills a whole column of websites at once; Refresh skips the cache.

Results are cached for 6 hours, so Sheets recalculating doesn't spend credits again. The key stays in your Google account.

Webhooks

Set a CRM webhook on the Integrations page and rows are POSTed to it as JSON batches while a sheet runs. Each delivery carries an X-Programmable-Signature header you can check with your signing secret; checking it is optional.

What a row costs

One credit a row, plus one for each of these column groups when a sheet asks for them: email (the email finder, on people sheets), leadership, performance and product_market. Find people adds one more per person found. AI columns and your own provider keys add nothing. Rows that can't be enriched are refunded at the same rate. JSON responses report credits_charged in the summary; with Accept: application/x-ndjson the response streams events, and the first (start) carries creditsPerRow.

Errors

Errors come back as {"error": "…"} with a plain-language message.

Rows are charged as they're built (see What a row costs); rows that fail are refunded.