> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/developer-resources/external-api/intelligems-external-api/available-endpoints.md). # Available Endpoints This is the authoritative list of endpoints. It is validated against the registered routes by an automated test, so it stays in sync and should not drift from the detailed per-endpoint pages. **Experiences** * `GET /v25-10-beta/experiences-list` — Retrieve a paginated list of experiences with optional filtering by `category`, `status`, and `module` * `GET /v25-10-beta/experiences/{experienceId}` — Get complete details for a specific experience * `POST /v25-10-beta/experiences` — Create a new experience or experiment * `PUT /v25-10-beta/experiences/{experienceId}` — Update an existing experience's configuration, variations, or targeting * `POST /v25-10-beta/experiences/{experienceId}/actions/{action}` — Perform a lifecycle action on an experience (`start`, `pause`, or `end`) **Experience & Experiment Analytics** * `POST /v25-10-beta/analytics/resource/{experienceId}` — Retrieve analytics for an experience (metrics, variations, optional graphs). Accepts filters and all request settings in the JSON body. Use this for all new integrations. * `POST /v25-10-beta/analytics/experience/{experienceId}/timeseries` — Metric-over-time data for a single experience * `POST /v25-10-beta/analytics/experience/{experienceId}/export` — Export an experience's analytics dataset * `GET /v25-10-beta/analytics/resource/{experienceId}` — *Deprecated.* Legacy query-parameter analytics endpoint, kept only as a beta compatibility path and removed when the beta ends. Use the POST variant above instead. **Sitewide Analytics** * `POST /v25-10-beta/analytics/sitewide/snapshot` — Summary KPI metrics with period-over-period percent changes and optional audience segmentation * `POST /v25-10-beta/analytics/sitewide/timeseries` — Metric-over-time data with configurable granularity and optional audience segmentation * `POST /v25-10-beta/analytics/sitewide/order-distribution` — Order-value histogram (KDE/CDF) and unit-mix breakdown * `POST /v25-10-beta/analytics/sitewide/conversion-funnel` — Sitewide conversion funnel as a Sankey graph (entry point → landing page → cart → checkout → conversion) **Holiday Benchmark** * `POST /v25-10-beta/analytics/event/snapshot` — Benchmark event snapshot metrics * `POST /v25-10-beta/analytics/event/timeseries` — Benchmark event metric-over-time data **Custom Events** * `PUT /v25-10-beta/custom-events` — Create a new custom event (click, scroll depth, page view, etc.), or update an existing one in place by passing back its `id` **Agentic Logic** * `GET /v25-10-beta/agentic-logic/rules` * `POST /v25-10-beta/agentic-logic/rules` * `GET /v25-10-beta/agentic-logic/rules/{ruleId}` * `PATCH /v25-10-beta/agentic-logic/rules/{ruleId}` * `DELETE /v25-10-beta/agentic-logic/rules/{ruleId}` * `GET /v25-10-beta/agentic-logic/rules/{ruleId}/draft` * `PUT /v25-10-beta/agentic-logic/rules/{ruleId}/draft` * `POST /v25-10-beta/agentic-logic/rules/{ruleId}/draft/validate` * `GET /v25-10-beta/agentic-logic/rules/{ruleId}/versions` * `GET /v25-10-beta/agentic-logic/rules/{ruleId}/versions/{version}` * `GET /v25-10-beta/agentic-logic/rules/{ruleId}/scenarios` * `POST /v25-10-beta/agentic-logic/rules/{ruleId}/evaluate-scenario` * `POST /v25-10-beta/agentic-logic/rules/{ruleId}/actions/{action}` * `POST /v25-10-beta/agentic-logic/rules/{ruleId}/publish` * `POST /v25-10-beta/agentic-logic/rules/{ruleId}/run-gates` * `POST /v25-10-beta/agentic-logic/rules/{ruleId}/cancel-checks` * `GET /v25-10-beta/agentic-logic/rules/{ruleId}/publish-jobs/{jobId}` * `PUT /v25-10-beta/agentic-logic/system-rules/{systemKey}` * `GET /v25-10-beta/agentic-logic/placements` * `POST /v25-10-beta/agentic-logic/placements` * `PATCH /v25-10-beta/agentic-logic/placements/{placementId}` * `DELETE /v25-10-beta/agentic-logic/placements/{placementId}` * `GET /v25-10-beta/agentic-logic/assignments` * `POST /v25-10-beta/agentic-logic/assignments` * `PATCH /v25-10-beta/agentic-logic/assignments/{assignmentId}` * `DELETE /v25-10-beta/agentic-logic/assignments/{assignmentId}` * `GET /v25-10-beta/agentic-logic/sources` * `POST /v25-10-beta/agentic-logic/sources/validate` * `GET /v25-10-beta/agentic-logic/sources/{name}` * `PUT /v25-10-beta/agentic-logic/sources/{name}` * `DELETE /v25-10-beta/agentic-logic/sources/{name}` * `POST /v25-10-beta/agentic-logic/sources/{name}/refresh` * `POST /v25-10-beta/agentic-logic/evaluate` * `GET /v25-10-beta/agentic-logic/exclusions` * `PATCH /v25-10-beta/agentic-logic/exclusions` Customer API keys select the organization. Agentic Logic must be enabled for that organization. Publish and run-gates requests return 202; poll the returned `publishJobId` for completion. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.intelligems.io/developer-resources/external-api/intelligems-external-api/available-endpoints.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.