Partnerbase Partnerships Scraper

Export partnerbase partnerships from supplied company pages into typed relationship rows for recurring alliance mapping. Each row connects a company to one visible partner, with the relationship type, company and pair URLs, and any employee, industry and external source-link context shown in the table.

This is a bounded initial-page snapshot, not a guaranteed complete ecosystem. Partnerbase currently displays up to 50 relationships in the initial company table. The Actor does not click Load More or paginate, and a company's advertised total can be much larger than the exported count.

Who is it for?

• Alliance teams refreshing a company watchlist before account planning.
• Market researchers comparing visible technology and channel partner relationships.
• Revenue operations teams loading source-linked relationship rows into spreadsheets or CRM enrichment pipelines.

Why use this Actor?

It returns normalized relationship records rather than raw HTML. Company and pair links are validated, mobile duplicates are excluded, and coverage fields distinguish a snapshot from an advertised ecosystem total. No source login, browser session, paid API key or proxy configuration is needed.

Getting started

1. Choose a company page such as https://www.partnerbase.com/salesforce.
2. Add it to Company URLs. Use company pages, not two-company pair pages.
3. Set a global Maximum relationships limit.
4. Run the Actor and inspect the default dataset.
5. Download JSON, CSV or Excel through Apify, or consume the dataset in your pipeline.

{
  "startUrls": [{"url": "https://www.partnerbase.com/salesforce"}],
  "maxItems": 10
}

Input parameters

Parameter	Default	Behavior
startUrls	Required	1–20 HTTPS Partnerbase company URLs, processed in order. Duplicate normalized URLs are fetched once.
maxItems	100	Integer 1–1000; global exported relationship cap across companies after within-company deduplication.

Only url is used from each request-list entry. Editor metadata (method, payload, headers, userData) is ignored; the Actor always uses GET. URLs must contain one company slug. Query parameters, fragments, credentials, other domains and pair/detail paths are rejected. Zero/unlimited limits and unknown input fields are rejected. A high maxItems value does not enable pagination. Billing or runtime limits can stop a run before its collection cap.

Extracted data

Field	Meaning
companyName, companyUrl	Identity of the supplied company.
partnerName, partnerUrl	Identity of the visible partner.
partnershipUrl	Partnerbase details URL for the pair; not visited by this Actor.
partnershipType	Visible type, such as Technology or Channel; null if absent.
employeeRange	Displayed partner employee range, not an exact headcount; nullable.
industry	Displayed partner industry; nullable.
sourceUrl	Optional external attribution URL; not fetched or independently verified.
totalPartners	Source-advertised company total, not export count; nullable.
visiblePartners	Distinct rows in the fetched initial table before maxItems truncation.
snapshotLimited	True when the advertised total exceeds visible rows, the total is unknown, or the user cap truncates the table.
scrapedAt	UTC timestamp for this company snapshot.

Output example

A real local Salesforce snapshot returned:

{
  "companyName": "Salesforce",
  "companyUrl": "https://www.partnerbase.com/salesforce",
  "partnerName": "Google",
  "partnerUrl": "https://www.partnerbase.com/google",
  "partnershipUrl": "https://www.partnerbase.com/google/salesforce",
  "partnershipType": "Channel",
  "employeeRange": "10,001+",
  "industry": "Software & Tech",
  "sourceUrl": "https://www.salesforce.com/news/press-releases/2023/06/07/salesforce-google-ai-partnership/",
  "totalPartners": 6622,
  "visiblePartners": 50,
  "snapshotLimited": true,
  "scrapedAt": "2026-10-03T20:11:29.799Z"
}

Source values may change. The record is an observation of Partnerbase's table, not independent confirmation of a current commercial partnership.

How much does it cost to export Partnerbase partnerships?

Pricing is pay per event: $0.005 per valid run started, plus one item event per exported relationship. No separate fee is charged for firmographic fields or attribution links. Invalid input fails before the start event; a valid run with no relationships still incurs the start event.

Apify spend tier	Price per relationship
FREE	$0.00276
BRONZE	$0.0024
SILVER	$0.001872
GOLD	$0.00144
PLATINUM	$0.00144
DIAMOND	$0.00144

At BRONZE, 10 exported relationships cost approximately $0.029, 50 cost $0.125, and 100 cost $0.245, including the start event. At FREE, 10 cost approximately $0.0326. These are estimates; check the current Pricing tab and your billing limit. Spend tiers depend on qualifying aggregate monthly Apify Store spend, not this Actor's private volume schedule. Infrastructure is covered by the Actor's event pricing; no external subscription is required.

Limits and failure behavior

Only the first visible table is collected. No history, monitoring, alerts, discovery search, guaranteed complete ecosystems or automated change detection is included. snapshotLimited: false means the source's displayed total agrees with the captured table; it is not independent proof of completeness.

A company-to-partner row is unique within that company snapshot. If both companies are supplied, the same pair may appear in two company contexts; use partnershipUrl to collapse those contexts downstream if desired.

Requests are sequential with a 30-second request timeout and at most three attempts for network failures, HTTP 429 or server errors. Stable client errors and parser/challenge failures stop the run. Previously exported records from a failed run are partial; do not treat them as a complete successful watchlist.

A recognized company page with an explicit zero partner count is a valid empty snapshot. Unrecognized pages or missing tables with positive/unknown counts fail instead of silently returning zero rows.

Integrations

Use Apify schedules to refresh the same input watchlist. Save each successful dataset externally and compare companyUrl + partnerUrl; this Actor does not maintain historical state. An absent relationship in a later bounded snapshot is not proof that the partnership ended.

Send dataset rows to Google Sheets, Airtable, Make, Zapier or a CRM pipeline using their Apify integrations. Preserve pair/source URLs and scrape timestamps for auditability. Export full datasets outside AI chat context when larger outputs are needed.

API usage

cURL

curl -X POST \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  'https://api.apify.com/v2/acts/automation-lab~partnerbase-company-partnerships/run-sync-get-dataset-items' \
  -d '{"startUrls":[{"url":"https://www.partnerbase.com/salesforce"}],"maxItems":10}'

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/partnerbase-company-partnerships').call({
  startUrls: [{ url: 'https://www.partnerbase.com/salesforce' }], maxItems: 10
});
const { items } = await client.dataset(run.defaultDatasetId).listItems({ limit: 10 });
console.log(items);

Python

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/partnerbase-company-partnerships').call(
    run_input={'startUrls': [{'url': 'https://www.partnerbase.com/salesforce'}], 'maxItems': 10})
print(client.dataset(run['defaultDatasetId']).list_items(limit=10).items)

MCP usage

Claude Code

claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/partnerbase-company-partnerships"

Claude Desktop, Cursor, and VS Code

Use your client's HTTP MCP settings with Apify authentication. Clients using mcpServers can use:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/partnerbase-company-partnerships"
    }
  }
}

VS Code uses its servers configuration format; put the same URL in an HTTP server entry. Keep authentication in client secret settings, not committed JSON.

Example prompt: “Export 10 visible Salesforce partner relationships and summarize the types, keeping source links and the coverage warning.”

Discover actual tools and argument schemas with scoped tools/list. Actor selection also adds run/storage helper tools; it does not expose exactly one tool. Discovery is read-only and is not permission to start a run.

For an authorized invocation, start once and retain the run ID, status and storage IDs. These are metadata, not result rows. If pending, follow that same run with bounded backoff (2, 4, 8 seconds, capped at 10) and a total deadline such as 120 seconds; do not restart on timeout. call-actor waits at most 45 seconds, so client timeouts must allow transport margin. At the deadline report pending with its run ID.

After success, read the returned dataset with explicit limit, offset and fields. Example consumer budget: pages of 20 rows, at most 100 source rows or 64 KiB serialized UTF-8 result content admitted to model context, whichever comes first. Enforce the byte ceiling host-side; if your client cannot intercept oversized responses, do not claim a hard guarantee. Report truncation and continuation offset. This consumer context budget does not change Actor collection limits.

Legality, responsible use and data handling

This unofficial Actor is not affiliated with or endorsed by Partnerbase or Crossbeam. Use the results responsibly and comply with applicable law, source terms and your data obligations. It collects public business relationship context, not personal contact lists. It does not use AI at runtime or send scraped rows to an AI provider.

Company URLs are sent to Partnerbase; outputs and logs are stored in your Apify run storage according to your account settings. The Actor creates no independent historical cache or session store. Delete datasets, key-value stores and logs through Apify when no longer needed; platform backups follow Apify's policy.

Failed operations send sanitized diagnostic input, exceptions and actor/build/run IDs to our private GlitchTip service for repair; secret fields and URL queries are removed and reports are retained for 30 days. No diagnostic credentials are exposed as inputs.

FAQ and troubleshooting

Why did I receive 50 rows when totalPartners says thousands? Only the initial visible page is exported. This is intentional bounded coverage, not full pagination.

Can I supply a pair URL or filter by industry? No. Supply company URLs; apply downstream filters to exported rows. Unknown fields are rejected rather than ignored.

Why did a run fail? Check that URLs identify real company pages without queries or fragments. A missing company, upstream challenge, source change or exhausted transient retries fails visibly. Inspect the run log and any partial rows.

Can I track changes? Schedule runs and compare successful snapshots externally. Source ordering and limited coverage can change; missing rows do not establish partnership termination.

Related workflows

This is a standalone alliance-relationship source. Company-directory Actors answer different firmographic questions and are not substitutes for partnership records. Find other tools in the automation-lab portfolio when you need a separate enrichment workflow.

Support

For a defect, use the Actor's Apify Issues tab and include your run URL, public company URL and expected behavior. Do not include passwords or private credentials.