Skip to main content
Manage Products programmatically using the 1eye API. Create, retrieve, update, and delete Product definitions to describe the solutions your business offers. Products are part of the 1eye Knowledge Base. They help 1eye understand your company’s offerings and evaluate buying activities related to those products. Changes made through the API are reflected in the 1eye Console, and vice versa.

Base URL

All Product API requests use:

Authentication

All endpoints require a valid 1eye API key.
API keys are scoped to a single workspace. All operations automatically apply to the workspace associated with your API key. You do not need to provide a workspace ID. The examples below use $API_KEY as the environment variable containing your API key. For more information, see Authentication.

Endpoints

All endpoints return JSON responses, except DELETE, which returns no response body.

Product Object

A Product defines a solution offered by your company, including its capabilities, target customers, and value proposition. For example, Snowbricks, a fictional cloud data and AI platform, offers a unified data platform combining cloud warehousing, lakehouse analytics, data engineering, and machine learning capabilities.

Fields

Example Product

System-Managed Fields

These fields are read-only and cannot be modified through Create or Update requests.

1. List Products

GET /v1/kb/products Retrieve a paginated list of Products configured in your workspace.

Query Parameters

Example Request

Example Response

200 OK

Pagination

When additional results are available, use pagination.next_cursor to retrieve the next page.
A null cursor indicates the end of the collection. See Pagination.

Behavior

  • Returns Products belonging to the authenticated workspace.
  • Excludes deleted Products.
  • Supports cursor-based pagination.
  • Returns an empty data array when no Products exist.

2. Retrieve a Product

GET /v1/kb/products/{id} Retrieve a specific Product using its unique identifier.

Path Parameters

Example Request

Example Response

200 OK

Behavior

  • Returns the complete Product record.
  • Includes system-generated metadata.
  • Returns 404 Not Found if the Product does not exist, has been deleted, or belongs to another workspace.

3. Create a Product

POST /v1/kb/products Create a new Product in your workspace. New Products become available to the relevant Buyer Intelligence and Market Signals processing logic.

Request Body

Example Request

Example Response

201 Created

Behavior

When a Product is created:
  1. 1eye generates a unique Product ID.
  2. The Product is associated with your workspace.
  3. The Product appears in the Knowledge Base.
  4. It becomes available to relevant future signal evaluation and buyer intelligence processing.
  5. It can be retrieved or updated through the API.
Important: Creating a Product does not automatically generate historical Signals or reevaluate existing Buyers.

Validation

  • name must not be empty.
  • short_name must not be empty.
  • description must not be empty.
  • short_name must be unique among active Products in the workspace.
  • System-managed fields cannot be supplied.

4. Update a Product

PATCH /v1/kb/products/{id} Update an existing Product. Only fields supplied in the request are modified.

Request Body

At least one editable field must be supplied.

Example Request

Example Response

200 OK

Behavior

  • Supports partial updates.
  • Preserves omitted fields.
  • Preserves the original Product ID.
  • Reflects changes in the Console.
  • Applies updated definitions to future processing.
Important: Updating a Product does not automatically reevaluate historical Buyers or Signals.

5. Delete a Product

DELETE /v1/kb/products/{id} Delete a Product from your workspace. Deletion performs a soft delete.

Example Request

Response

204 No Content The response body is empty.

What Happens When a Product Is Deleted?

  • The Product is removed from the active Knowledge Base.
  • It no longer appears in List Products.
  • Retrieving the deleted record returns 404 Not Found.
  • It is excluded from future product-related processing.
  • Historical Product information and associated Signals remain preserved.
Deleting a Product does not delete Buyers, Signals, or historical evaluations. Restoring deleted Products is not currently exposed through the public API.

6. How Products Affect Buyer Intelligence

Product definitions help 1eye understand what your business sells and identify relevant buying activity. For example, Snowbricks might define:

Products vs. Topics

For example: Product: Snowbricks Data Cloud Topic: Lakehouse Architecture A Product describes a specific offering. A Topic describes an area of market interest that may indicate demand for that offering.

Market Signals

Products may provide context for product-related Market Signals, including the explored_product trigger. 1eye uses the existing Signal Intelligence pipeline to identify relevant activity.

Impact of Product Changes

Console Synchronization

Changes made through the API are reflected in the 1eye Console, and vice versa.

7. Error Handling

All Product endpoints use the standard 1eye API error format.

Example Error

404 Not Found
See Errors.

8. Pagination & Rate Limits

List Products supports cursor-based pagination.
  • Default page size: 100.
  • Maximum page size: 1,000.
  • Use cursor for subsequent pages.
  • next_cursor: null indicates the end of the collection.
Product API requests count toward your workspace API rate limits. See Pagination and Rate Limits.

9. Best Practices

Define Meaningful Products

Create Products corresponding to distinct customer-facing solutions. Avoid creating multiple Products that describe the same offering.

Use Consistent Short Names

Describe What the Product Does

Include the Product’s:
  • Primary capabilities.
  • Target customers.
  • Business problems solved.
  • Key use cases.
  • Relevant technologies.
  • Differentiating capabilities.

Separate Products from Topics

A Product should represent what you sell. A Topic should represent what your buyers are researching.

Keep Product Definitions Current

Update descriptions when capabilities, positioning, or use cases change.