# Developer Platform Welcome to your team’s developer platform ## Documentation Home

:server:

Database ReferenceBrowse our datasets, check out the sources and data categories, dive into the data dictionaries, and preview sample records./spaces/tSRArD4olBq5gWyQgvBn/files/IaUMODRBBSBL8eUaPX09

:terminal:

API ReferenceSee how to plug fresh, real-time data directly into your systems. Tap into public web insights on professionals, organizations, jobs, and activities./spaces/3Q759Fy8BEGDuLlT93sy/files/ebMoLMpZFyLqpzByuzrk
{% columns %} {% column %} ### About ScrapIn Since 2020, ScrapIn has been powering global businesses with reliable B2B data. Over 400 companies trust us for fresh insights on organizations, people, jobs, and activities. With more than 1.5B user data requests each month, we provide both datasets and real-time APIs to ensure your data stays instantly refreshed. {% endcolumn %} {% column %}
{% endcolumn %} {% endcolumns %} # Dataset Quickstart Welcome to the preview documentation of our Dataset offer. This documentation is designed to give you a clear overview of: * **How data is delivered** (formats & integrations) * **What data is available** (coverage, fields, freshness) * **How to get started** (sales & onboarding process) Our goal is to make accessing and using our data as **simple and frictionless** as possible. Whether you need bulk datasets or continuous updates, our team ensures that delivery is smooth and adapted to your infrastructure. {% hint style="info" %} #### Important Note Access to the full dataset is available through our **sales process**. This preview documentation is here to help you understand the scope of our data and how easy it is to integrate once you’re onboard.\ \ Book a call with us {% endhint %} # Delivery Format We provide flexible access to our data, so your team always gets the information in the right format, at the right time. You can choose between 4 different flat file datasets format. | Format | Pros | Cons | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | **JSON** | - Human-readable and widely used- Nested structures supported- Great for APIs and web data | - Large file sizes (not space-efficient)- Slower to parse on big datasets- Harder to process in batch (not line-delimited) | | **JSONL** (JSON Lines) | - Line-delimited, easy to stream and process- Works well with big data pipelines (can split files easily)- Still human-readable | - Less widely adopted than plain JSON- No built-in schema enforcement- Slightly less convenient for nested arrays than JSON | | **CSV** | - Very simple and widely supported- Compact for tabular data- Easy to open in Excel/Sheets | - No support for nested/complex data- No types (everything is text)- Ambiguities with delimiters, quoting, encoding | | **Parquet** | - Highly compressed and columnar (great for analytics)- Efficient for large-scale queries (only reads needed columns)- Schema + data types preserved- Optimized for big data tools (Spark, Hive, Snowflake) | - Not human-readable- Higher overhead for small datasets- More complex libraries needed to read/write | *** ### What does the data look like? When you choose to export or receive data, you can select different formats. Each format represents the data in a different way. Here’s what you can expect: #### **1. JSON (JavaScript Object Notation)** ```json { "id": 1, "name": "Alice", "email": "alice@example.com", "skills": ["Python", "SQL"] } ``` **Key points:** * A **human-readable text file** used almost everywhere. * Stores data as objects with keys (`"name"`, `"email"`) and values. * Can handle lists, nested objects, and complex structures. **When to use it:** * Great for structured data that needs to be read or shared easily. * Widely used in APIs and integrations. #### **2. JSONL (JSON Lines)** **What it looks like:** ```json {"id": 1, "name": "Alice", "email": "alice@example.com"} {"id": 2, "name": "Bob", "email": "bob@example.com"} {"id": 3, "name": "Charlie", "email": "charlie@example.com"} ``` **Key points:** * Each **line in the file** is its own JSON object. * Easy to process line by line, especially with large files. * Lighter and faster than a big JSON array for bulk data. **When to use it:** * Perfect for **large-scale data processing** (Spark, Elasticsearch, etc.). * Useful for **logs, events, or streaming-style data**. #### **3. CSV (Comma-Separated Values)** **What it looks like:** ```csv id,name,email 1,Alice,alice@example.com 2,Bob,bob@example.com 3,Charlie,charlie@example.com ``` **Key points:** * A **simple text table**, with each row as a record and each column separated by a comma (sometimes semicolon). * Opens easily in Excel, Google Sheets, or any spreadsheet tool. * Doesn’t support nested or complex data—everything is flattened into rows and columns. **When to use it:** * Best for **simple tabular data**. * Ideal if you want to quickly view and manipulate your data in Excel. #### **4. Parquet** **What it looks like:** * You **cannot open a Parquet file in a normal text editor**. * It’s a **binary, compressed format** optimized for storage and analytics. **Example (using Python/Pandas):** ```python import pandas as pd df = pd.read_parquet("data.parquet") print(df.head()) ``` Output (table view): ``` id name email 0 1 Alice alice@example.com 1 2 Bob bob@example.com 2 3 Charlie charlie@example.com ``` **Key points:** * Stores data with proper types (numbers, strings, dates, etc.). * Very efficient in terms of **size** and **query performance**. * Supported by all major data tools (Snowflake, BigQuery, Spark, etc.). **When to use it:** * Best for **large datasets**. * Ideal for **analytics pipelines** and **machine learning workloads**. *** # Sending Methods We deliver data either via direct download or directly into your chosen cloud storage, including Amazon S3 and Google Cloud Storage | **Direct Download** | We provide a secure link and login credentials so you can retrieve the data directly. | | ------------------------ | -------------------------------------------------------------------------------------- | | **Amazon S3** | Share your S3 storage credentials, and we’ll deliver the data straight to your bucket. | | **Google Cloud Storage** | Provide your GCS credentials, and we’ll transfer the data to your storage. | | **Microsoft Azure** | Provide your Azure storage credentials, and we’ll send the data directly to you. | ### What tools do you recommend? Working with large datasets requires the right combination of technologies to efficiently manage storage, processing, and transformation at scale. Below are some categories and examples of tools commonly used for big data workloads: | **Tool Category** | **Examples** | | ---------------------------------------- | ---------------------------------------------------------------------------------------------------- | | **Database systems** | MongoDB, Couchbase, PostgreSQL, Apache Cassandra, Amazon Redshift, Amazon S3 + Athena, Elasticsearch | | **Data processing frameworks** | Apache Spark, Apache Hadoop | | **Data ingestion tools** | Apache NiFi, Google BigQuery | | **ETL (Extract, Transform, Load) tools** | AWS Glue, Talend | | **Data transformation** | dbt, Pandas | # Data Overview {% hint style="info" %} You’re viewing a preview of our documentation. The full version—available to clients—provides in-depth data stats, onboarding resources, changelogs, FAQs, and additional details Access full documentation {% endhint %} Our datasets offers **comprehensive global coverage** of professionals and companies.\ It includes detailed records across multiple geographies, industries, and job levels. **High-level statistics:** * **Profiles:** \~**610M million** individual profiles * **Companies:** \~**65M million** company records * **Geographies covered:** 200+ countries & territories * **Industries represented:** 50+ industries (IT, Finance, Healthcare, Manufacturing, etc.) ### Data Fields | Category | Data Type | Description | | ------------------- | ------------------ | ---------------------------------------------------------------------------------- | | **Person Profile** | Identity | Full name, social profile URL, and headline — core identifiers of the professional | | | Current Position | Job title, company name, domain, and industry of the current role | | | Career History | Past roles and companies, with dates when available | | | Education | Schools, degrees, fields of study, and graduation years | | | Skills & Languages | List of declared skills and languages when available | | | Network & Activity | Connection count ranges, recent activity signals (posts, likes, comments) | | | Media | Profile picture URL if public | | **Company Profile** | Company Identity | Company name, LinkedIn URL, domain, and industry classification | | | Size & Structure | Company size ranges, number of employees on LinkedIn, headquarters location | | | Background | Founding year and company specialties | | | Workforce Signals | Employees present on LinkedIn, hiring activity, job postings | | | Technology & Tools | Technologies used (when detectable) | ### Data Freshness We ensure our database remains **up-to-date and reliable**. * **Daily updates:** 5 to 20 millions of profiles and companies updated * **Change tracking:** We monitor career moves, job changes, and company updates in real time One of the key advantages of our database is that it is continuously refreshed thanks to our **live API infrastructure**. Unlike static databases that rely on monthly or quarterly updates, our system processes **millions of real-time requests every day**. This means that whenever a profile or company detail changes — for example a new job title, a company switch, or a fresh job posting — our system is designed to capture and reflect those changes immediately. Because of this constant stream of updates, the **majority of our database is fully refreshed every month**, ensuring that our clients always work with **up-to-date and reliable information**. In short, our **live update pipeline** transforms our database into a living ecosystem, always aligned with the latest professional movements and company dynamics. *** ### Data Completeness Not all fields are filled for every profile — but we track coverage to maintain transparency.\ Here’s an example (to be completed with your real stats): | Field | Coverage Rate | Notes | | ----------------------- | ------------- | --------------------------------------- | | Full Name | 100% | Always available | | Social Profile URL | 100% | Always available | | Professional Experience | 75% | Some profiles may not specify | | Current Company | 65% | Some freelancers/consultants not linked | | Education | 30% | Not all users fill education | | Skills | 9% | Optional field | | Email / Phone (if any) | 10% | Limited availability, not always public | # Quickstart {% hint style="warning" %} **Important Notice** This documentation is only a **preview** of our API. It provides a high-level overview of what the API can do and which types of data objects you can expect.\ \ The **official API Reference** — including full technical specifications, JSON schemas, sample results, error codes, and authentication details — is only available after signing up to our platform.\ \ Sign up to access the full API Reference {% endhint %} *** This QuickStart is designed to help you quickly understand: * **What our API does**: the main endpoints available and the kind of data they deliver. * **How to use it**: what inputs are required and what objects are returned. * **Where it fits**: common use cases such as sales enrichment, recruiting workflows, CRM integration, or analytics pipelines. It’s **not a technical deep dive**, but a way to educate you and your team on the possibilities of the API before accessing the full reference. *** ### How It Works 1. **Explore endpoints in this preview**\ Each endpoint page explains at a high level: * What the endpoint does. * The inputs it accepts (e.g., Social URL, name, domain). * The outputs it returns (structured person, company, or activity objects). * Typical use cases and benefits. 2. **Understand delivery & integration**\ Data can be delivered via simple API calls or bulk delivery formats (CSV, JSON, Parquet, etc.), depending on your needs.\ Our team can also help with **cloud integrations** (Amazon S3, Google Cloud, Azure). 3. **Get full access**\ To access the **full API Reference** (with technical specifications, JSON examples, error codes, and complete object schemas), you need to **sign up for the platform** and get credentials. # Person Profile Endpoint The **Person Profile** endpoint allows you to retrieve a complete and structured person profile from a Social URL. It is the fastest way to enrich a single person record with professional, educational, and contextual company information. This endpoint is ideal when you already have a social profile link and need to transform it into structured data. | Aspect | Description | | ------------ | --------------------------------------------------------------------------------------------------------------------- | | **Purpose** | Convert a Social profile URL into a structured **person object** with job, education, skills, and context. | | **Input** | A Social profile URL (e.g., `https://www.social.com/janedoe`). | | **Output** | A JSON object containing identity, career history, education, skills, and a linked **company object** when available. | | **Credits** | Each successful call consumes **1 credit**. | | **Best for** | Lead enrichment, recruiting snapshots, updating contact records before outreach. | ### Objects structure The response is divided into two main objects: #### **Person object** Includes all information related to an individual’s LinkedIn profile, such as: * **Identity:** First name, last name, headline, Social URL, profile photo. * **Location:** City, region/state, country. * **Professional signals:** Current title and company, follower count, premium/badge info. * **Career history:** List of past roles and companies with dates. * **Education:** Schools, degrees, fields of study, and dates. * **Skills & languages:** Declared skills and spoken languages. * **Certifications:** Certificates and issuing organizations, when available. #### **Company object** Provides structured context about the person’s current company: * Company name, Social URL, domain, and industry. * Employee count and size range. * Headquarters location. * Founded year. * Website, tagline, and description. {% hint style="warning" %} **Important Notice** This documentation is only a **preview** of our API. It provides a high-level overview of what the API can do and which types of data objects you can expect.\ \ The **official API Reference** — including full technical specifications, JSON schemas, sample results, error codes, and authentication details — is only available after signing up to our platform.\ \ Sign up to access the full API Reference {% endhint %} # Person Match Endpoint The **Person Match** endpoint allows you to retrieve a complete and structured person profile starting from partial information such as **name, company, domain, or email**.\ It is designed for cases where you don’t already have a Social URL but need to identify and enrich the correct profile automatically. This endpoint is ideal when you have limited datapoints and want to match them to the right person profile on social networks. | Aspect | Description | | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Purpose** | Identify and enrich the correct person using partial data (name, company, domain, email) — no Social URL required. | | **Input** | Any combination of: **first/last name**, **company name**, **company domain**, **email** (work or personal), and optionally **location** for disambiguation. | | **Output** | A structured **person object** and a linked **company object** when available. Responses may include basic **match metadata** (e.g., resolved Social URL, match status). | | **Credits** | Typically **1 credit** per successful match (adjust to your billing rules). | | **Best for** | CRM enrichment without URLs, deduplication, contact resolution, recruiting lookups, and data quality workflows. | ### Objects Structure The response is divided into two main objects: #### **Person object** Includes all information related to an individual’s profile, such as: * **Identity:** First name, last name, headline, Social URL, profile photo. * **Location:** City, region/state, country. * **Professional signals:** Current title and company, follower count, premium/badge info. * **Career history:** List of past roles and companies with dates. * **Education:** Schools, degrees, fields of study, and dates. * **Skills & languages:** Declared skills and spoken languages. * **Certifications:** Certificates and issuing organizations, when available. #### **Company object** Provides structured context about the person’s current company: * Company name, Social URL, domain, and industry. * Employee count and size range. * Headquarters location. * Founded year. * Website, tagline, and description. {% hint style="warning" %} **Important Notice** This documentation is only a **preview** of our API. It provides a high-level overview of what the API can do and which types of data objects you can expect.\ \ The **official API Reference** — including full technical specifications, JSON schemas, sample results, error codes, and authentication details — is only available after signing up to our platform.\ \ Sign up to access the full API Reference {% endhint %} # Company Profile Endpoint The **Company Profile** endpoint lets you extract a structured company record starting from a **Social URL**. It’s the fastest way to enrich a single company with identity, size, web presence, HQ, and brand information, returned as a clean JSON object. | Aspect | Description | | ------------ | ---------------------------------------------------------------------------------------------------------------------------------- | | **Purpose** | Convert a company **Social URL** into a structured **company object** you can use in CRM/CDP, analytics, or enrichment workflows. | | **Input** | A **company Social URL** (e.g., your canonical company page URL on the target social network). | | **Output** | A JSON object containing company identity, size & reach, web/brand info, HQ details, and basic metadata (plus rate-limit/credits). | | **Credits** | Typically **1 credit** per successful call (align with your billing rules). | | **Best for** | Company enrichment, account mapping, firmographic normalization, and pre-outreach verification. | ### Objects Structure The response is centered on a single **Company object.** #### Company object High-level fields you can expect: * **Company Identity** — Name, **Social URL**, normalized handle, internal/company id when available. * **Size & Reach** — Employee count and **size range**; follower/subscriber counts when available. * **Web & Brand** — Website URL, industry classification, **tagline**, and **description**. * **Headquarters & Basics** — HQ location (city, country, region), postal code/streets when available, **founded year**. * **Media & Visuals** — Logo and cover/background image URLs (when present). * **Specialties** — Keywords describing the company’s areas of focus. {% hint style="warning" %} **Important Notice** This documentation is only a **preview** of our API. It provides a high-level overview of what the API can do and which types of data objects you can expect.\ \ The **official API Reference** — including full technical specifications, JSON schemas, sample results, error codes, and authentication details — is only available after signing up to our platform.\ \ Sign up to access the full API Reference {% endhint %} # Company Search Endpoint The **Company Search** endpoint lets you **find and list companies** based on flexible filters (name, domain, industry, size, location, keywords, etc.).\ Use it when you **don’t have a Social URL** yet and need to discover or shortlist the right companies before enrichment. | Aspect | Description | | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Purpose** | Discover companies that match your criteria and return them as structured company objects. | | **Input** | Any combination of filters such as: **company name**, **domain**, **industry**, **size range**, **location** (city/region/country), and **keywords**. Supports **pagination** and optional **sorting** (e.g., relevance, followers, employee count). | | **Output** | A **list of company objects** plus **metadata** (pagination cursors/pages, total count if available) and optional **match/relevance scores**. | | **Credits** | Typically **1 credit** per successful call (or per page), depending on your billing policy. | | **Best for** | Account discovery, market mapping, ABM list building, territory planning, data QA before enrichment. | ### Objects Structure #### Company object * **Company Identity** — Name, **Social URL**, normalized handle/ID, and domain. * **Size & Reach** — Employee count and **size range**; follower/subscriber counts when available. * **Web & Brand** — Website URL, industry classification, **tagline**, **description**, and specialties (keywords). * **Headquarters & Basics** — HQ location (city/region/country), and **founded year**. * **Media & Visuals** — Logo and cover/background image URLs when present. {% hint style="warning" %} **Important Notice** This documentation is only a **preview** of our API. It provides a high-level overview of what the API can do and which types of data objects you can expect.\ \ The **official API Reference** — including full technical specifications, JSON schemas, sample results, error codes, and authentication details — is only available after signing up to our platform.\ \ Sign up to access the full API Reference {% endhint %} # Person Social Activities These endpoints let you explore and retrieve a person’s **public activity**: posts they authored, comments they wrote, reactions they gave, and full details for a specific post (including its comments, reactions, and reposts). Use them to power **sales intel**, **recruiting research**, **influencer mapping**, and **engagement analytics**. *** ### 1) Posts List recent **posts authored** by a person identified by a Social URL (or by a previously resolved person ID). | Aspect | Description | | ------------ | ---------------------------------------------------------------------------------------------- | | **Purpose** | Discover a person’s recent authored content (thought leadership, announcements, hiring notes). | | **Input** | Person **Social URL** or **personId**; optional **pagination** and **time window**. | | **Output** | A **list of post objects** plus **pagination metadata**. | | **Credits** | Typically **1 credit per call/page** (align with your billing policy). | | **Best for** | Sales/recruiting research, content relevance, engagement scoring. | #### Objects Structure * `activityId` — unique identifier of the post * `text` — post content * `reactionsCount`, `commentsCount` — engagement counters * `activityDate` — timestamp of the post * `author` — object with `authorId`, `authorName`, `authorPublicIdentifier`, `authorHeadline`, `authorImage`, `authorUrl` * `activityUrl` — Social URL of the post * `shareUrl` — share link *** ### 2) Comments List recent **comments authored** by the person across various posts. | Aspect | Description | | ------------ | --------------------------------------------------------------------------- | | **Purpose** | Understand **where and how** the person engages (topics, people, brands). | | **Input** | Person **Social URL** or **personId**; optional **pagination/time window**. | | **Output** | A **list of comment objects** with references to the **parent post**. | | **Credits** | Typically **1 credit per call/page**. | | **Best for** | Interest mapping, influencer analysis, competitor monitoring. | #### Objects Structure * `text` — comment text * `reactionsCount` — reactions to this comment * `commentsCount` — replies under this comment * `activityDate` — timestamp of the comment * `author` — block with `authorId`, `authorName`, `authorPublicIdentifier` * `activityUrl` — Social URL to the comment * `relatedPost` — object of the parent post (`activityId`, `text`, etc.) *** ### 3) Reactions List recent **reactions** (likes, celebrates, etc.) made by the person on other posts. | Aspect | Description | | ------------ | ---------------------------------------------------------------------------- | | **Purpose** | Reveal the person’s **interests and affinities** via their reaction history. | | **Input** | Person **Social URL** or **personId**; optional **pagination/time window**. | | **Output** | A **list of reaction objects** tied to **post references**. | | **Credits** | Typically **1 credit per call/page**. | | **Best for** | Interest graph building, ABM signal scoring, prospect research. | #### 🧩 Objects Structure * `reactionId` — unique ID * `type` — reaction type (like, celebrate, insightful, etc.) * `createdAt` — timestamp of the reaction * `post` — block with `activityId`, `text`, `author`, `activityUrl` *** ### 4) Post Details Retrieve the **full details of a single post** using its ID or Social URL. | Aspect | Description | | ------------ | ------------------------------------------------------------------------------ | | **Purpose** | Access complete content and engagement stats of a single post. | | **Input** | `activityId` or `activityUrl` — required. | | **Output** | A **post object** with full details. | | **Credits** | 1 credit per call. | | **Best for** | Post analytics, storing/archiving, connecting with comments/reactions/reposts. | *** ### 5) Post Comments Retrieve the **comments under a specific post**. | Aspect | Description | | ------------ | ----------------------------------------------- | | **Purpose** | Explore the audience’s replies under a post. | | **Input** | `activityId` or `activityUrl` — required. | | **Output** | A list of **comment objects** tied to the post. | | **Credits** | 1 credit per call (per page). | | **Best for** | Engagement analytics, sentiment research. | *** ### 6) Post Reactions Retrieve the **reactions on a specific post**, including reaction type and (when available) the reacting users. | Aspect | Description | | ------------ | --------------------------------------------------------- | | **Purpose** | Understand who engaged with a post and how. | | **Input** | `activityId` or `activityUrl` — required. | | **Output** | A list of **reaction objects** (user + type + timestamp). | | **Credits** | 1 credit per call (per page). | | **Best for** | Audience mapping, ABM signal scoring, influencer prep. | *** ### 7) Post Reposts Retrieve the **reposts (shares)** of a post, including who reshared it and when. | Aspect | Description | | ------------ | --------------------------------------------------------------------- | | **Purpose** | Measure amplification and reach through reshares. | | **Input** | `activityId` or `activityUrl` — required. | | **Output** | A list of **repost objects** (reposter + date + optional commentary). | | **Credits** | 1 credit per call (per page). | | **Best for** | Virality analysis, campaign measurement, influencer tracking. | {% hint style="warning" %} **Important Notice** This documentation is only a **preview** of our API. It provides a high-level overview of what the API can do and which types of data objects you can expect.\ \ The **official API Reference** — including full technical specifications, JSON schemas, sample results, error codes, and authentication details — is only available after signing up to our platform.\ \ Sign up to access the full API Reference {% endhint %} # Company Activities Endpoints These endpoints let you explore a company’s **public activity**: the posts it publishes, and the engagement around those posts (comments, reactions, reposts). Use them to power **account research, competitor monitoring, content analytics, and ABM signals**. *** ### 1) Company Posts Retrieve recent **posts** (activity updates) published by a company based on its Social URL (or equivalent identifier). | Aspect | Description | | ------------ | --------------------------------------------------------------------------------------------- | | **Purpose** | Get the public posts published by a company. | | **Input** | `socialUrl` (company’s Social page URL) — required. Optional `page` parameter for pagination. | | **Output** | A list of **post objects** + metadata (pagination, credits, rate limits). | | **Credits** | 1 credit per successful call. | | **Best for** | Account research, content strategy, competitor monitoring. | #### 🧩 Objects Structure (post) * `activityId` — unique identifier of the post * `text` — textual content of the post * `reactionsCount`, `commentsCount` — engagement counters * `activityDate` — timestamp of publication * `author` — object with `authorId`, `authorName`, `authorPublicIdentifier`, `authorHeadline`, `authorImage`, `authorUrl` * `activityUrl` — Social URL of the post * `shareUrl` — shareable link to the post * `metadata` — pagination info: `currentPage`, `pageNumber`, `perPage`, `total` *** ### 2) Company Post Retrieve **detailed data for one specific post** of a company, given its `activityId` or Social URL. | Aspect | Description | | ------------ | --------------------------------------------------------------------------------- | | **Purpose** | Get full details of a single company post. | | **Input** | `activityId` (the post’s ID) — required. | | **Output** | A **post object** with full details. | | **Credits** | 1 credit per request. | | **Best for** | Detailed post analytics, linking to sub-endpoints (comments, reactions, reposts). | #### 🧩 Objects Structure (post) * `activityId` * `text` * `reactionsCount`, `commentsCount` * `activityDate` * `author` (with identity fields) * `activityUrl`, `shareUrl` * `relatedPost` — optional, if it’s a reshared post *** ### 3) Post Comments Retrieve **all comments** made on a specific company post. | Aspect | Description | | ------------ | -------------------------------------------------------------------- | | **Purpose** | See the conversation under a specific post. | | **Input** | `activityId` (post’s ID) — required. Optional `page` for pagination. | | **Output** | A list of **comment objects** + metadata. | | **Credits** | 1 credit per call/page. | | **Best for** | Engagement analysis, sentiment tracking, community insights. | #### 🧩 Objects Structure (comment) * `text` — content of the comment * `reactionsCount` — number of reactions on the comment * `commentsCount` — number of replies under the comment * `activityDate` — timestamp of the comment * `author` — object with `authorId`, `authorName`, `authorPublicIdentifier` * `activityUrl` — Social URL of the comment *** ### 4) Post Reactions Retrieve the **reactions** on a specific company post — who reacted and what type of reaction. | Aspect | Description | | ------------ | -------------------------------------------------------------------- | | **Purpose** | Understand which users engaged with the post and how. | | **Input** | `activityId` (post’s ID) — required. Optional `page` for pagination. | | **Output** | A list of **reaction objects** + metadata. | | **Credits** | 1 credit per call/page. | | **Best for** | Audience mapping, engagement tracking, campaign analytics. | #### 🧩 Objects Structure (reaction) * `type` — type of reaction (e.g., LIKE) * `author` — object with `authorId`, `authorName`, `authorUrl` *** ### 5) Post Reposts Retrieve the **reposts (shares)** of a company post — who reshared it and when. | Aspect | Description | | ------------ | -------------------------------------------------------------------- | | **Purpose** | Measure amplification and reach of company content. | | **Input** | `activityId` (post’s ID) — required. Optional `page` for pagination. | | **Output** | A list of **repost objects** + metadata. | | **Credits** | 1 credit per call/page. | | **Best for** | Virality analysis, campaign measurement, influencer mapping. | #### 🧩 Objects Structure (repost) * `activityDate` — timestamp of the repost * `author` — object with `authorId`, `authorName`, `authorPublicIdentifier` * `activityUrl` — Social URL of the repost * `commentary` — optional text added by the reposter {% hint style="warning" %} **Important Notice** This documentation is only a **preview** of our API. It provides a high-level overview of what the API can do and which types of data objects you can expect.\ \ The **official API Reference** — including full technical specifications, JSON schemas, sample results, error codes, and authentication details — is only available after signing up to our platform.\ \ Sign up to access the full API Reference {% endhint %} # Compliance New updates and improvements At ScrapIn, we value transparency in our data privacy practices and support our partners in making informed choices. We are dedicated to the responsible collection of web data, with a strong focus on safeguarding personal information and ensuring security. ### What data does ScrapIn collect? ScrapIn collects data from both publicly available sources and trusted online environments. Our datasets include company information such as firmographics, funding rounds, job postings, and product reviews, along with business-related insights about professionals. All data is handled responsibly, with strict security standards and compliance processes in place. To ensure responsible use of data, ScrapIn does **not** collect: * Private personal data that requires a direct connection on social networks or personal relationships. * Sensitive personal information, even if publicly visible — such as social security numbers, residential addresses, geolocation details, or biometric identifiers. ### Compliance with global standards We closely monitor privacy regulations worldwide, including the **General Data Protection Regulation (GDPR)** in Europe and the **California Consumer Privacy Act (CCPA)** in the United States. * We continuously adapt our practices in response to evolving case law, regulatory guidance, and industry standards. * We implement **data minimization principles**, meaning we only process data strictly necessary for our services. * Our infrastructure follows strict **security protocols** to protect data integrity and prevent misuse. ### User rights & opt-out We respect the rights of individuals regarding their personal data. * If you would like to request the removal of your information, you can **submit an opt-out request** directly through our website. * We provide clear guidance for individuals to manage how their data is used or displayed online. ### Contact us If you have any questions about our compliance practices, please contact us at ****.