Splash 360 website screenshot

Splash 360

French vendor of point-of-sale and management software for collective catering — company restaurants, school and institutional canteens. The product line covers a smart till, self-service ordering kiosks and kiosk software, Wifi Order, a Kitchen Display System, a back-office management layer, a coin handler, and loyalty through a YouFid integration. NO PUBLIC API SURFACE: the company sells and deploys into catering operators directly, and publishes no developer portal, API documentation or machine-readable contract. That is the absence of a PUBLIC interface, not the absence of APIs — a till, a kiosk and a kitchen display exchanging orders are API-driven by construction, but those interfaces reach customers through deployment and integration work rather than a public developer program.

Splash 360 is profiled on the APIs.io network. Tagged areas include Point-of-Sale, Collective Catering, Food Service, Restaurant Technology, and Kiosk.

Splash 360’s developer surface includes engineering blog and 1 more developer resources.

2.1/100 minimal ▬ flat Agent 0/100 human only Front door AI 1/6 silent Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0
0 APIs
Point-of-SaleCollective CateringFood ServiceRestaurant TechnologyKioskKitchen DisplayLoyaltyBack OfficeFranceHospitality

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/splash360: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Resources

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: splash360
name: Splash 360
description: 'French vendor of point-of-sale and management software for collective catering — company restaurants, school
  and institutional canteens. The product line covers a smart till, self-service ordering kiosks and kiosk software, Wifi
  Order, a Kitchen Display System, a back-office management layer, a coin handler, and loyalty through a YouFid integration.
  NO PUBLIC API SURFACE: the company sells and deploys into catering operators directly, and publishes no developer portal,
  API documentation or machine-readable contract. That is the absence of a PUBLIC interface, not the absence of APIs — a till,
  a kiosk and a kitchen display exchanging orders are API-driven by construction, but those interfaces reach customers through
  deployment and integration work rather than a public developer program.'
url: https://raw.githubusercontent.com/api-evangelist/splash360/refs/heads/main/apis.yml
x-api-posture: no-product-api
x-api-posture-basis: observed
x-api-posture-note: 'NO PUBLIC API SURFACE: the company sells and deploys into catering operators directly, and publishes
  no developer portal, API documentation or machine-readable contract.'
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
created: '2026-08-19'
modified: '2026-08-19'
specificationVersion: '0.23'
tags:
- Point-of-Sale
- Collective Catering
- Food Service
- Restaurant Technology
- Kiosk
- Kitchen Display
- Loyalty
- Back Office
- France
- Hospitality
tags_raw:
- Point of Sale
- Collective Catering
- Food Service
- Restaurant Technology
- Kiosk
- Kitchen Display
- Loyalty
- Back Office
- France
- Hospitality
apis: []
common:
- type: Website
  url: https://splash360.fr
- type: Blog
  url: https://splash360.fr/blog
maintainers:
- FN: Splash 360
  url: https://splash360.fr
x-evidence:
  round: '2026-08-19'
  admitted_from: Add-API parked queue, submission splash-360-fdc34922, gate confidence 3, reason no_consumable_surface.
  why_listed_not_dropped: no_consumable_surface is not sufficient grounds to drop. The question is whether this is a real
    company on a domain it owns, and it is. splash360.fr returns 200 with 223,583b and a real product site; an invented path
    returns a genuine 404, so the host discriminates. A valid company with no public API gets listed and scores low — the
    low score is the point, and it is what gives the vendor something to act on.
  dev_surface_probed_2026_08_19: /api, /developers, /developpeurs, /docs, /openapi.json, /apis.json and /llms.txt all return
    404. Probed with a browser user-agent, so these are real absences and not a bot-protection artifact masking them.
  wording: Recorded as no PUBLIC API surface rather than no APIs. Tills, kiosks and kitchen displays exchanging orders are
    API-driven by construction; those interfaces simply do not reach a public developer program.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/splash360"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/splash360/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/splash360/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.