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

6sense Company API

The Company API from 6sense — 1 operation(s) for company.

6sense Company API is one of 5 APIs that 6sense publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Company. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 3 JSON Schemas.

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

Requests are made against a single base URL, https://epsilon.6sense.com.

7 operations 7 paths 9 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://epsilon.6sense.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

6sense Company API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (TokenAuth). An API key is passed in the header as Authorization (API_KEY).

  • TokenAuth — Token-based auth. Format: Token .

Paths & Operations 7

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

Company 7
GET
/v3/company/details
Get Company Details By IP
getCompanyDetails 3 params → 200401404429
GET
/v1/company/products
getProductsList → 200400401402403
GET
/company/v1/segment/{segment_id}deprecated
getAccountsList 1 param → 200400401402403
GET
/company/v1/segmentsdeprecated
getSegments → 200400401402403
GET
/v1/company/segment/{segment_id}deprecated
getAccountsList_1 1 param → 200400401402403
GET
/v1/company/segmentsdeprecated
getSegments_1 → 200400401402403
GET
/v1/company/validate_access/segmentsdeprecated
validateSegment → 400401402403

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Company (29 properties), ProductScore (7 properties), CompanyDetailsResponse (4 properties), Account (3 properties). Each schema is shown below with its type and property counts.

ProductScore
object
7 properties
CompanyDetailsResponse
object
4 properties
Segments
object
3 properties
Company
object
29 properties
ProductResponse
object
2 properties
ErrorResponse
object
2 properties
OrgToSegmentsResponse
object
3 properties
Account
object
3 properties
SegmentAccountsResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

6sense-company-api-openapi.yml Raw ↑

Other APIs 6sense publishes across the network.

6sense Enrichment API
6sense People API
6sense MCP Server
6sense Scoring API
Where this information came from

This is an independent, third-party profile of 6sense Company 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.