Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sellfern.com/llms.txt

Use this file to discover all available pages before exploring further.

Sellfern is designed to be clear for AI agents, automation tools, and human developers. This guide explains how an agent should discover available documentation, choose safe actions, and avoid unsupported API behavior.

​
Start with the docs index

Agents should begin with: 
https://docs.sellfern.com/llms.txt
Use that index to discover product pages, developer guides, and the API Reference before making assumptions.

​
Use only V1-ready public endpoints

The API Reference is generated from Sellfern’s curated public V1 OpenAPI spec. Treat it as the source of truth for public endpoint availability. If an endpoint is not present in the API Reference, treat it as unavailable for public integrations.

​
Authentication

Use scoped API keys with the x-api-key header: 
curl https://api.sellfern.com/orders \
  -H "x-api-key: $SELLFERN_API_KEY"
Never use browser session JWTs for server-to-server integrations.

​
Scopes

Request the minimum scope required for the user’s goal. If Sellfern returns 403 missing_scope, ask the user for an API key with the minimum additional scope.

​
Organization isolation

API keys are scoped to one organization. If Sellfern returns 404 not_found, do not infer that the resource exists in another organization.

​
Writes and retries

For public write endpoints, send an Idempotency-Key header. Reuse the same key when retrying the same logical mutation after a timeout or uncertain 5xx response. Generate a new key for a different logical mutation.

​
Avoid unavailable surfaces

Do not use or recommend admin, debug, cron, internal, deferred bulk, sync, import, fulfillment, broad financial, or non-public endpoints unless they appear in the V1 API Reference.
  1. Read llms.txt.
  2. Read the relevant product page to understand user intent.
  3. Read the relevant developer guide for authentication, errors, idempotency, and scopes.
  4. Confirm endpoint availability in the API Reference.
  5. Use the minimum required API call.
  6. Explain any missing scope, unavailable endpoint, or unsafe request to the user before proceeding.