How to Enrich a List of LinkedIn URLs (in Ruby)

You can enrich a list of LinkedIn URLs in Ruby with one standard-library script: read the URLs, call POST /v1/people/enrich for each, wait out any 429, and write the answers to a CSV. This guide gives you that script and explains each part.

TL;DR

• One Ruby file, 33 lines, no gems. It reads urls.txt and writes people.csv.
• Time: about 10 minutes to set up. At 4 requests a second, 1,000 URLs take at least 4 minutes.
• Cost: 1 LeadOcean record per URL we hold a match for. A miss is a 404 and is free, so the Free plan's 1,000 records cover up to 1,000 matches.

Prerequisites

• Ruby 3.0 or newer. Only the standard library is used (net/http, json, csv).
• A LeadOcean API key, exported as $LEADOCEAN_API_KEY. The Free plan gives you one with 1,000 records for life, no card.
• A urls.txt file with one LinkedIn profile URL per line.

Step 1: Get a key and prepare the list

Sign up at app.leadocean.io, create a key and put it in your shell. Never write the key into the source file.

export LEADOCEAN_API_KEY="your-key-here"
printf '%s\n' \
  "https://www.linkedin.com/in/jane-doe-acme" \
  "https://www.linkedin.com/in/john-roe-acme" > urls.txt

The enrich endpoint takes exactly one identifier per call: linkedin_url, email, phone or person_id. Enrich does not page. You make one call per URL, so "paging" here means walking your file line by line.

Step 2: Write the Ruby script

Save this as enrich.rb. Requests go to https://api.leadocean.io with the x-api-key header.

require "net/http"
require "json"
require "csv"

URI_ENRICH = URI("https://api.leadocean.io/v1/people/enrich")
KEY = ENV.fetch("LEADOCEAN_API_KEY")

def enrich(url)
  5.times do
    req = Net::HTTP::Post.new(URI_ENRICH, "x-api-key" => KEY, "Content-Type" => "application/json")
    req.body = { linkedin_url: url, reveal_email: true }.to_json
    res = Net::HTTP.start(URI_ENRICH.host, URI_ENRICH.port, use_ssl: true) { |h| h.request(req) }
    if res.code == "429"
      sleep [res["Retry-After"].to_i, 1].max
      next
    end
    return [res.code, res.body]
  rescue SocketError, Net::OpenTimeout, Net::ReadTimeout
    sleep 1
  end
  ["0", "gave up after 5 tries"]
end

CSV.open("people.csv", "w") do |csv|
  csv << %w[linkedin_url status json]
  File.foreach("urls.txt", chomp: true) do |line|
    url = line.strip
    next if url.empty?
    status, body = enrich(url)
    csv << [url, status, body]
    sleep 0.25
  end
end

Three choices in that script matter:

• reveal_email: true returns the contact points on the record. It adds no extra record.
• The 0.25 second pause keeps you at 4 requests a second, under the Free plan's limit of 5.
• On a 429 the code reads Retry-After, sleeps that many seconds, and tries again, up to 5 times. See API rate limits and 429 errors.

Step 3: Run it

ruby enrich.rb
head -3 people.csv

The status column tells you what happened per URL: 200 is a match, 404 is nobody found. Filter on it before you load rows anywhere else.

Step 4: Parse the fields you need

The CSV stores the raw JSON so you lose nothing. When you know which fields you want, call JSON.parse(body) and read them from the result. The current role is in contact_current_experiences[] and phones are in contact_phones[].phone. Since October 2026 the same call also returns career history in resume_data: past roles, education, certifications and awards.

require "csv"
require "json"

CSV.foreach("people.csv", headers: true) do |row|
  next unless row["status"] == "200"
  person = JSON.parse(row["json"])["data"]
  contact = person["contact_data"] || {}
  email = (contact["contact_emails"] || [{}]).first["email"]
  puts [person.dig("profile_data", "profile_full_name"), contact["email_status"], email].join(",")
end

Past employers carry no company_id yet. If you need a company record, call POST /v1/companies/enrich with the domain.

What you get

The response shape from the API reference, with placeholder values. This is not a real person.

{
  "success": true,
  "data": {
    "profile_data": { "profile_full_name": "Jane Doe", "profile_headline": "VP Sales at Acme" },
    "contact_data": {
      "has_email": true,
      "email_status": "verified",
      "contact_emails": [{ "email": "jane.doe@acme.com", "type": "work", "status": "verified" }],
      "contact_phones": [{ "phone": "+1 415 555 0133", "type": "mobile" }],
      "contact_current_experiences": [{ "job_title": "VP Sales", "company_name": "Acme" }]
    },
    "resume_data": { "experiences": [], "educations": [], "certifications": [] }
  },
  "meta": { "key_hash": "...", "fetched_at": "2026-10-01" }
}

Source: response shape from the API reference (openapi.json, October 2026), with field names from the enrich docs. Each record also carries a fetched_at date, and the dataset refreshes monthly.

Troubleshooting

FAQ