Skip to content
Technology

Technology That Makes Complex Workflows Simpler.

Every Talvexio product is delivered online, in three ways. Here's how each one works.

SubscriptionsBulk processingAPI access
Online software subscriptions

Use the software in your browser, on a subscription.

Our products are hosted web applications. Sign in through a browser and run the tools from your account, with no server software to install or maintain.

  • Hosted web applications
  • Sign in through a browser
  • No servers to set up or maintain
  • Job status visible in your account
Bulk data processing

Upload a whole file. Download it finished.

Large files run as background jobs, so a long run doesn't hold up the person who started it. Results come back with a status for what was and wasn't found.

  • CSV and XLSX files
  • Background jobs with a visible status
  • Duplicates removed
  • A result on every row
leads.csv5 rows, sample data
First nameWork emailStatus
AdaEmptyEmpty
JonasEmptyEmpty
PriyaEmptyEmpty
TomasEmptyEmpty
MeiEmptyEmpty
API access

Run the same work from your own systems.

A REST API lets your product or automation tool submit jobs, check their status and collect the results, without anyone opening a browser.

  • REST API
  • Submit, poll and download
  • Rate limits and idempotency keys
  • Works with automation tools
POST /v1/jobs
Authorization: Bearer YOUR_API_KEY
Idempotency-Key: 7f3a-sample

{
  "type": "email_verification",
  "input_file": "contacts.csv"
}
Response
{
  "id": "job_8f2c",
  "status": "submitted"
}

An illustrative example of the job flow, not a published reference. Talk to us about API access and we'll go through the details.

Ask about API access
How we build

What we care about when we build software

  • Product engineering

    We scope each product around one job and build the workflow before adding options. A narrow scope makes a product easier to explain, test and improve.

  • Software integrations

    Data is only useful where people already work. Depending on the product, results can move through CSV and XLSX files, CRMs, sending tools or automation platforms.

  • Scalability

    We treat volume as a design constraint from the start. Bulk jobs, queues and rate limits let usage grow in a controlled way.

  • User experience

    Status, cost and results should be visible without reading a manual. In practice that means job statuses, a cost preview before a job runs, and a state on each returned field.

  • Data quality

    A filled-in field isn't the same as a correct one. Results come back with a status for what was and wasn't found, so you can decide what to do with each.

  • Continuous improvement

    Shipping is the start of the work. We keep improving products after release, fixing rough edges and adding what people need.