When you already know which companies you care about—maybe they’re leads, customers, or competitors—the Company API gives you a fast, structured way to pull up-to-date information about them.

Rather than searching manually or scraping pages, this API lets you fetch key company details using just a public company profile link or domain.

It’s perfect for enriching company records, validating your data, or powering custom workflows where accurate company insights matter.

A standard Company API call may return details like:

You can exclude fields you don’t need to reduce credit usage.

The Company API includes multiple endpoints for accessing different types of company-related data.

Each endpoint supports its own set of fields and request options. To view the full list of available endpoints and stay up to date with current capabilities, refer to the official documentation:

👉 View the Company API Documentation

You send a request with either:

The API returns a JSON response with available data. The more specific and complete the source, the higher the accuracy.

A basic Company Profile Endpoint request usually costs 1 credit.

However, your credit usage may increase if:

{

"funding_data": "include",

"exit_data": "include",

"acquisitions": "include"

}

To minimize credit use, exclude extra fields and disable data freshness unless you need the latest updates.
​

Every API response includes a `last_updated` timestamp showing when the company data was last retrieved:
​

```json

{

"meta": {

"last_updated": "2023-10-26T11:34:30Z",

"thin_profile": false

}

}

```
​

Enrich Layer processes approximately 2 billion profile checks per month to keep data current. When you use `use_cache=if-recent`, data less than 29 days old is returned from cache—older data triggers a fresh scrape.
​

🔒Privacy-Restricted Profiles
​

When `thin_profile` is `true`, privacy settings limit data access. You'll receive cached data but cannot refresh. You won't be charged for failed refresh attempts.

💡 Set your default `use_cache` in dashboard settings to avoid specifying it in every request.
​

You can set your default `use_cache` behavior directly in your Enrich Layer dashboard, which applies to all API requests unless overridden by request-level parameters.
​

1. Log into your Enrich Layer dashboard

2. Navigate to your API settings or configuration section

3. Locate the Data Freshness preferences
​

Choose your default `use_cache` value:

- `if-present` (default): Uses cached data whenever available - most cost-effective option

- `if-recent`: Only uses cache data from the last 29 days, automatically pulls fresh data for older profiles (costs +1 additional credit per profile when fresh data is retrieved)
​

By default, both toggles are disabled (meaning `use_cache=if-present` is used for most cost-effective operation).
​

Understanding the relationship between dashboard settings and API parameters:
​

- Dashboard setting: Establishes your baseline behavior for all API calls

- Request-level parameter: Overrides your dashboard default for specific requests

- Priority: Request-level parameters always take precedence over dashboard defaults
​

Example: If your dashboard default is `if-present`, but you include `use_cache=if-recent` in a specific API request, that request will use `if-recent`.
​

💡 Best Practice: Set your dashboard default to match your most common use case, then override it only when needed for specific requests. This eliminates the need to specify `use_cache` in every single API call.

Use this API when you want to:

Not sure if it fits your use case? Test it with a public profile URL in Postman or your preferred tool. You’ll see right away what data comes back—and what it costs.

​