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 Reverse Email Lookup API

The Reverse Email Lookup API from Enrich — 4 operation(s) for reverse email lookup.

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

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

This API exposes 4 operations across 4 paths, and defines 32 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.

4 operations 4 paths 32 schemas 2 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 Reverse Email Lookup 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 4

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

Reverse Email Lookup 4
POST
/reverse-lookup/bulk-lookup
Look up professional profiles in batch
bulkReverseLookup body → 200400401402429500
GET
/reverse-lookup/bulk-lookup/{batchId}
Check bulk lookup progress
getBulkLookupStatus 1 param → 200401404429
GET
/reverse-lookup/bulk-lookup/{batchId}/results
Get bulk lookup results
getBulkLookupResults 3 params → 200401404429
POST
/reverse-lookup/lookup
Look up a professional profile by email
reverseLookup body → 200400401402429500

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are ReverseLookupResult (19 properties), ReverseLookupResult_2 (19 properties), BatchResultsMeta_2 (6 properties), BulkLookupSubmitData_2 (6 properties). Each schema is shown below with its type and property counts.

PositionHistoryItem
object
One entry in a person's work history
6 properties
BulkLookupResponse
object
3 properties 2 required
BatchStatusResponse
object
3 properties 2 required
BulkLookupRequest
object
2 properties 1 required
BatchStatusData
object
Progress information for a batch job
5 properties 2 required
ErrorEnvelope
object
RFC 9457 Problem Details error response.
5 properties 3 required
ReverseLookupResult
object
Professional profile data for a person
19 properties
BulkLookupSubmitData
object
Returned when you submit a bulk reverse lookup
6 properties 3 required
ReverseLookupResponse
object
3 properties 2 required
BulkLookupResultsResponse
object
3 properties 2 required
LookupRequest
object
1 property 1 required
BatchResultsMeta
object
Metadata returned when you fetch batch results (includes credit settlement)
6 properties
StartEndDate
object
A date range (used for job history and education)
2 properties
BatchSubmitMeta
object
Metadata returned when you submit a batch job
4 properties
EnrichmentMeta
object
Metadata included with every enrichment response
4 properties
EducationHistoryItem
object
One entry in a person's education history
5 properties
PositionHistoryItem_2
object
One entry in a person's work history
6 properties
BulkLookupResponse_2
object
3 properties 2 required
BatchStatusResponse_2
object
3 properties 2 required
BulkLookupRequest_2
object
2 properties 1 required
BatchStatusData_2
object
Progress information for a batch job
5 properties 2 required
ErrorEnvelope_2
object
RFC 9457 Problem Details error response.
5 properties 3 required
ReverseLookupResult_2
object
Professional profile data for a person
19 properties
BulkLookupSubmitData_2
object
Returned when you submit a bulk reverse lookup
6 properties 3 required
ReverseLookupResponse_2
object
3 properties 2 required
BulkLookupResultsResponse_2
object
3 properties 2 required
LookupRequest_2
object
1 property 1 required
BatchResultsMeta_2
object
Metadata returned when you fetch batch results (includes credit settlement)
6 properties
StartEndDate_2
object
A date range (used for job history and education)
2 properties
BatchSubmitMeta_2
object
Metadata returned when you submit a batch job
4 properties
EnrichmentMeta_2
object
Metadata included with every enrichment response
4 properties
EducationHistoryItem_2
object
One entry in a person's education history
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

enrich-so-reverse-email-lookup-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 API
Enrich Company Followers/Count Estimation API
Enrich Email Validation API
Enrich Enrich API
Enrich IP to Company API
Enrich Wallets API
Where this information came from

This is an independent, third-party profile of Enrich Reverse Email Lookup 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.