Slider Endpoint

NEW v2.22.0 · Presentation Slides

Slider Endpoint

Manage all promotion slides ( slider and slider_description tables) via the JSON API: export, create, update, and delete.


Endpoints

MethodEndpointScopeDescription
GET/Export/JSON/slidersslider:readAll Slides
GET/Export/JSON/slider/{id}slider:readSingle Slide
GET/Export/JSON/sliders/{from}:{to}slider:readID Range
POST/Import/JSON/sliderslider:writeCreate New Slide
PUT/Import/JSON/sliderslider:writeUpdate slide (slider_id required)
DELETE/Delete/JSON/slider/{id}slider:deleteDelete slide + all language variants

Filter (Export)

  • ?status=0|1 — active / inactive slides only
  • ?type={n} — Slide type (0 = image, 1 = video, …)
  • ?categories_id={n} — Slides in a category (internally maps to entity_type=category)
  • ?content_id={n} — Slides on a CMS page (internally maps to entity_type=content)
  • ?language=de|en — only one language (ISO code or language_id)

Payload Structure

{
  "type": "slider",
  "data": [
    {
      "slider_id": 11,
      "slider_status": 1,
      "sort_order": 100,
      "entity_type": "content",
      "entity_id": 0,
      "target": "",
      "type": 0,
      "date_from": "2026-01-01",
      "date_till": "2026-12-31",
      "shop_ids": "1",
      "languages": {
        "de": {
          "title": "Slide-Titel",
          "description": "

HTML

", "direction": "left", "width": 8, "image": "images/slider/large/slide.png", "image_mobile": "", "video": "", "video_mobile": "" } } } ] }

Notes

  • Starting with Shop 4.8: entity_type (category / content / news) + entity_id determine the target object; clients that still sendcategories_id/content_id must update their code (these fields are ignored).
  • PUT expects slider_id in the payload; if it is missing, the API responds with a 400 MISSING_ID error.
  • A POST request with a slider_id that has already been assigned returns a 409 Already exists error—use PUT in this case.
  • DELETE removes both the slide row and all associated slider_description rows(all languages).
  • Background: Until now, slides could only be managed via the backend. This endpoint is suitable, for example, for correcting incorrect slide links after the fact using PUT /slider.