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

Surfe People API

Search and enrich individual contacts.

Surfe People API is one of 4 APIs that Surfe publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include People. 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 16 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.surfe.com/v2.

4 operations 4 paths 16 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.surfe.com/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Surfe People API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Surfe API key issued from the Surfe dashboard, sent as Authorization: Bearer {api-key}.

Paths & Operations 4

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

People 4

Search and enrich individual contacts.

POST
/people/search
Search people
searchPeople body → 200401402429
POST
/people/enrich
Enrich people (start)
startPeopleEnrichment body → 202401402429
GET
/people/enrich/{id}
Enrich people (get)
getPeopleEnrichment 1 param → 200401404429
POST
/people/find-by-email
Find people by email
findPeopleByEmail body → 200401429

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Person (10 properties), PersonInput (6 properties), CompanyFilters (6 properties), PeopleSearchRequest (5 properties). Each schema is shown below with its type and property counts.

EnrichedPerson
PeopleEnrichmentRequest
object
4 properties 2 required
PersonInput
object
6 properties
JobStatus
string
PeopleFilters
object
Person-based filters.
4 properties
JobHistoryEntry
object
5 properties
EmailRecord
object
3 properties
Person
object
10 properties
PeopleEnrichmentResult
object
4 properties
Range
object
2 properties
CompanyFilters
object
Company-based filters.
6 properties
Error
object
2 properties
PeopleSearchResponse
object
3 properties
EnrichmentJobAccepted
object
3 properties
PeopleSearchRequest
object
5 properties 1 required
PhoneRecord
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

surfe-people-api-openapi.yml Raw ↑

Other APIs Surfe publishes across the network.

Surfe Account API
Surfe Companies API
Surfe Recommendations API
Where this information came from

This is an independent, third-party profile of Surfe People 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.