Build on the Nesika API

Everything you can do in the Nesika app is available through our public, versioned REST API. Search products, compare competitor prices, pull price history, read market insights, and access your own workspace data -- all with a single API key.

API-first platform access

The public API covers the same platform capabilities your team uses in the app. Endpoints are versioned under /api/v1/so integrations can evolve safely over time.

Product Matching

Search products and work with competitor matches for your workspace catalog.

Price Monitoring

Read current prices, price history, time series, and trend data.

Pricing Actions

Pull cost analysis and pricing action data for decision support.

Competitor Intelligence

Compare competitor assortments, prices, and market position.

Market Insights

Access insight cards and market signals your team can act on.

Account and Usage Data

Use /api/v1/me/* endpoints to inspect your account, workspace, usage, and limits.

Interactive reference and spec

The live reference lets you browse every endpoint, inspect request and response schemas, review examples, and run live requests after pasting your API key. The base URL is shown at the top of the reference.

Open interactive API reference Download OpenAPI spec (JSON)

Generate an API key

API keys are created from your workspace settings and are used for programmatic access outside the first-party app.

Open Settings

Go to Settings and the API management tab.

Generate a key

Click Generate key, give the key a clear name, and choose an expiration that matches its purpose.

Copy the key immediately

Copy the key as soon as it appears. The full key is shown only once.

Store it securely

Save the key in an environment variable or secret manager before using it in scripts, services, or automation tools.

Keys are shown once

Never commit API keys to source control. If a key is lost or exposed, revoke it and create a replacement. For key management details, see API Keys.

Authenticate with X-API-Key

Include your key in every request using the X-API-Key request header. Bearer and JWT authentication is for the first-party app; third-party and programmatic access uses API keys.

curl -H "X-API-Key: <your-key>" "https://nesika-ase-prod-webapi-prod.azurewebsites.net/api/v1/products/search?q=iphone"

Build with an AI agent

The API is agent-ready. Coding agents, MCP clients, and code generation tools can consume the machine-readable OpenAPI spec directly, then call the same public endpoints available to developers.

For agent developers

Each endpoint includes scenario-oriented descriptions so an agent can understand when and why to call it. Request and response schemas plus examples are included in the spec.

Agent setup checklist

Fetch the OpenAPI spec from the machine-readable spec URL.
Generate a client or feed the spec into your agent's tool layer.
Authenticate every API call with the X-API-Key header.

Rate limits and quotas

API usage is metered per plan. If you exceed your quota, the API returns HTTP 429 Too Many Requests with rate-limit headers. Build in retry logic with backoff so your integration recovers gracefully.

Plan for backoff

Check rate-limit headers before retrying high-volume jobs. For key limits and request-window details, see the API Keys rate limits section.