How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Enrich Company Followers API

The Company Followers API from Enrich — 7 operation(s) for company followers.

Enrich Company Followers API is one of 18 APIs that Enrich publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Company Followers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 7 paths, and defines 24 schemas. It is described by OpenAPI 3.2.0, at version 3.0.

Requests are made against a single base URL, https://dev.enrich.so/api/v3.

7 operations 7 paths 24 schemas 5 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0
Base URL
https://dev.enrich.so/api/v3
Authentication
API Key, HTTP Bearer, apikey, bearer
Contact
Terms of Service
Resource Areas
1

Authentication & Security 4

Enrich Company Followers API declares 4 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyHeader). It accepts HTTP bearer tokens (BearerToken). It defines a apikey scheme (apiKey). It defines a bearer scheme (bearerAuth).

  • ApiKeyHeader — API key in the x-api-key header. Documented at https://doc.enrich.so/authentication-1951026m0
  • BearerToken — The same API key sent as an Authorization: Bearer token.
  • apiKey — Your API key. Keys start with sklive and are 64 characters long.
  • bearerAuth — Alternative — send the same key as a Bearer token: Authorization: Bearer sklive...

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 5 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Company Followers 7
POST
/company-follower
Continue company follower scrape
continueCompanyFollowerScrape 1 param body → 200400401402404409410422
GET
/company-follower/limit
Check daily scraping limit
checkCompanyFollowerLimit → 200401429500
GET
/company-follower/{batchId}/export
Export results as CSV
exportCompanyFollowerCsv 1 param → 200400401404429
GET
/company-follower/{batchId}/progress
Check scrape progress
getCompanyFollowerProgress 1 param → 200401404429
GET
/company-follower/{batchId}/results
Get scrape results
getCompanyFollowerResults 3 params → 200401404429
POST
/count-estimate
Start count estimation
startCountEstimate body → 200400401402429500
GET
/count-estimate/{batchId}
Get estimation status/results
getCountEstimateStatus 1 param → 200401404429

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are FollowerProfile_2 (22 properties), FollowerProfile (22 properties), CompanyFollowerProgressData (7 properties), CompanyFollowerProgressData_2 (7 properties). Each schema is shown below with its type and property counts.

CompanyFollowerResultsData
object
4 properties 4 required
SeniorityBreakdownItem
object
4 properties 4 required
CountEstimateResultData
object
4 properties 1 required
CompanyFollowerProgressResponse
object
3 properties 2 required
ErrorEnvelope
object
RFC 9457 Problem Details error response.
5 properties 3 required
StartCompanyFollowerResponse
object
3 properties 2 required
StartCompanyFollowerData
object
2 properties 2 required
CompanyFollowerProgressData
object
7 properties 5 required
CompanyFollowerResultsResponse
object
3 properties 2 required
FunctionBreakdownItem
object
5 properties 4 required
CountEstimateStatusResponse
object
3 properties 2 required
FollowerProfile
object
22 properties 1 required
CountEstimateRequest
object
6 properties 1 required
StartCountEstimateResponse
object
3 properties 2 required
StartCountEstimateData
object
6 properties 2 required
CountEstimateStatusData
object
7 properties 4 required
CompanyFollowerResultsData_2
object
4 properties 4 required
StartCompanyFollowerData_2
object
2 properties 2 required
ErrorEnvelope_2
object
RFC 9457 Problem Details error response.
5 properties 3 required
CompanyFollowerProgressResponse_2
object
3 properties 2 required
StartCompanyFollowerResponse_2
object
3 properties 2 required
CompanyFollowerProgressData_2
object
7 properties 5 required
CompanyFollowerResultsResponse_2
object
3 properties 2 required
FollowerProfile_2
object
22 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

enrich-so-company-followers-api-openapi.yml Raw ↑

Other APIs Enrich publishes across the network.

Enrich Email Finder API
Enrich Lead Finder API
Enrich Phone Finder API
Enrich Teams API
Enrich People Search API
Enrich Authentication API
Enrich Company Followers/Count Estimation API
Enrich Email Validation API
Enrich Enrich API
Enrich IP to Company API
Enrich Reverse Email Lookup API
Enrich Wallets API
Where this information came from

This is an independent, third-party profile of Enrich Company Followers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.