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.
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/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/splash360/"><img src="https://apis.io/badge/splash360/card.svg" alt="Splash 360 on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Machine-Readable Auth+10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
13 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
gated: private
gated_source:
- x-api-posture
label: Unknown
confidence: low
source: []
generated: '2026-11-06'
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.