Decathlon
Utilities & PersonalConnect AI agents to Decathlon's public sports intelligence APIs. Agents look up sports, resolve places where they are played, and read the referential data behind Decathlon's catalog.
What This Integration Enables
Decathlon publishes something companies usually build badly for themselves: a maintained taxonomy of sports, and a geographic index of the places they are played. Not a product catalog. A referential. The Sports API carries names, descriptions, slugs, tags, and the relationships between sports, including parents, children, related sports, and groups, plus a search that matches against synonyms and lexical fields and reindexes results by geolocalized popularity. The Sport Places API carries venues as GeoJSON with contact details, addresses, and per-place activities, alongside the referential of which tags and filters are legitimate for each sport. Anyone who has watched an in-house activity dropdown drift over three years, until "running" and "trail running" and "jogging" are three unrelated options nobody maintains, knows why a published taxonomy with stable identifiers is worth more than the effort saved.
Say plainly what this connector is: thirteen actions, all reads. There is no write here at all, no submission, no place creation, no activity posting. Every action calls a public Decathlon read endpoint that requires no authentication. On the sports side, List Sports returns the full catalog with optional filters for parent sports only, sports with an icon, or sports matched to Decathlon master data, and Get Sport retrieves one by numeric ID or slug such as swimming. Search Sports performs an intelligent match against synonyms, lexical fields, tags, and descriptions, and Get Sport Recommendations returns the most popular sports for a location; both require coordinates. List Sport Groups and Get Sport Group give the high level organization. On the places side, List Places searches by bounding box or by an origin with a radius, neither exceeding 100km, capped at 100 results per page, and Get Place retrieves one by UUID or slug. List Place Activities returns what is offered at a venue with attributes such as difficulty, duration, distance, and elevation gain, while List Place Sports, Get Place Sport, Get Sport Allowed Filters, and Get Sport Allowed Tags return the vocabulary allowed per sport. Decathlon publishes no event subscription and this service ships no triggers, which is exactly what you would expect of a reference API: reference data does not happen to you, you go and read it on a schedule or in response to something else.
Two details decide whether a flow built on this is right or subtly wrong. Coordinates are formatted as longitude,latitude, the reverse of several other standards. And Get Sport Recommendations does not simply fail when it cannot serve your exact point: it finds the nearest city with valid contextual data and ranks from there.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A sport picker that matches how people actually search
A booking or membership product needs a sport selector, and the in-house list has been accumulating synonyms for years. On a schedule the agent calls List Sports for the full catalog with names, slugs, tags, and relationships, and List Sport Groups for the higher level organization, then writes both to Google Sheets or into the product's own store. Search Sports handles the runtime half, matching a user's typed query against synonyms, lexical fields, tags, and descriptions rather than against exact names, so "spinning" and "footy" land somewhere sensible. Get Sport Allowed Tags and Get Sport Allowed Filters then constrain what a user may say about an activity for that sport, which turns a free text field into a validated one. The relationships matter here too, because parent and child sports let the interface offer a broad choice that narrows rather than a flat list of four hundred entries.
Venue lookup that respects the API's own limits
A team wants nearby venues for a sport a customer expressed interest in. The agent calls List Places with either a bounding box, supplying the South West and North East corners together, or a central origin with a radius, and it stays inside the documented ceilings: neither the bounding box nor the radius may exceed 100km, and results cap at 100 per page. Places come back as a GeoJSON FeatureCollection with contact details, address, and activities per place, and Get Place retrieves the full record for one by UUID or slug. List Place Activities then reports what is actually offered there, with difficulty, duration, distance, and elevation gain, which is the difference between "there is a pool nearby" and "there is a pool nearby that runs beginner lessons." The results go to the customer through Gmail or into a HubSpot record.
Location-aware content that names the location it assumed
A content or campaign flow wants to lead with the sports that are genuinely popular in a region rather than the ones the marketing team plays. The agent calls Get Sport Recommendations for the region's coordinates, which ranks sports by geolocalized popularity, and Search Sports for the specific terms under consideration, since search results are also reindexed by popularity near the supplied point. It then assembles the draft and, critically, carries the resolved location through to the review step rather than discarding it, for the reason set out below. The approved copy goes out through the channel that owns it, and the sports and slugs used are recorded in Google Sheets so the same set can be reused rather than re-derived.
Human-in-Loop Highlight
This connector cannot break anything. It has no writes. So the honest gate is not on a Decathlon call, it is on the first act downstream that reaches a real audience, and it is anchored on a specific behavior Decathlon documents about its own API. Get Sport Recommendations does not require your coordinates to correspond to a place it knows about. From the supplied point it finds the nearest city with valid contextual data and ranks sports by popularity there. Search Sports does the same thing in a quieter form, reindexing results by geolocalized popularity near the coordinates you gave it. Neither returns an error for a location it cannot serve, because from the API's point of view nothing went wrong. Now add the other detail: coordinates here are longitude,latitude, the reverse of several other standards. Transpose the pair, as anyone integrating against a system that uses the other convention eventually will, and 45.51,-73.58 stops being Montreal and becomes a point in the Indian Ocean, from which the API dutifully finds the nearest city with valid data and returns a confident, well-formed, entirely plausible ranking of sports. A campaign goes out recommending the wrong region's sports to a real audience, and every log line in the flow says success. So the agent surfaces the thing the API resolved rather than the thing it was asked. Before any location-derived output is sent, published, or written to a customer record, it posts to the owner in Slack: "Regional sports campaign for the Montreal list. I passed coordinates -73.5827,45.5120 as longitude,latitude to Get Sport Recommendations. Decathlon resolved that to its nearest city with valid contextual data and ranked: ice hockey, running, cycling, swimming, climbing. List Places found 47 venues for the top three inside a 25km radius, and the first three addresses are on Rue Sainte-Catherine, Avenue du Parc, and Boulevard Saint-Laurent. Those addresses are my only evidence the coordinates landed where I think they did. Send to 4,200 contacts, or should I check the coordinate order first?" A person reads three street names and knows in a second what no assertion count could tell them. That is the shape of human-in-the-loop orchestration on a read-only reference API: the gate is not permission to act, it is a person confirming that a confident answer is an answer to the right question.
Agent Capabilities
13 actionsSports Catalog
6- List Sports Returns the full catalog of sports from the Decathlon Sports API, each with its name, description, slug, tags, and relationships (parent, children, related sports, group, images). No authentication is required. Optional filters narrow the list to parent sports only, to sports with an icon, or to sports matched to Decathlon master data.
- Get Sport Retrieves a single sport from the Decathlon Sports API by its numeric ID or its slug, for example swimming. Returns the sport name, description, icon, tags, and relationships to parent, children, related sports, and group. No authentication is required.
- Search Sports Performs an intelligent search of the Decathlon Sports API by matching the query against sport synonyms, lexical fields, tags, and descriptions, which is why it finds sports users name in ways the catalog does not. Results are reindexed by the geolocalized popularity of the sports near the supplied coordinates. Coordinates are required and formatted as longitude,latitude. No authentication is required.
- Get Sport Recommendations Returns the most popular sports for a location from the Decathlon Sports API. From the supplied coordinates it finds the nearest city with valid contextual data and ranks sports by geolocalized popularity, which means a point it does not recognize produces a valid answer for somewhere else rather than an error. Coordinates are required and formatted as longitude,latitude. No authentication is required.
- List Sport Groups Retrieves all sport groups from the Decathlon Sports API. Groups give a high level view of how sports are organized and related, each listing the sports it contains. No authentication is required and this endpoint accepts no parameters.
- Get Sport Group Retrieves a single sport group from the Decathlon Sports API by its numeric ID or slug, for example water-aerobics, including the list of sports that belong to it. No authentication is required.
Sport Places
3- List Places Searches the Decathlon Sport Places API for sport places matching geographic and activity criteria, returned as a GeoJSON FeatureCollection with contact details, address, and activities per place. Provide either a bounding box (South West and North East corners together) or a central origin with a radius. A bounding box or radius must not exceed 100km, and results are limited to 100 per page. This read endpoint requires no authentication.
- Get Place Retrieves a single sport place from the Decathlon Sport Places API by its UUID or slug, returned as a GeoJSON Feature with contact details, address components, and the list of activities offered at that place. This read endpoint requires no authentication.
- List Place Activities Retrieves the list of sporting activities offered at a specific place, each with its sport ID, tags, title, and filter attributes such as difficulty, duration, distance, and elevation gain. This is what distinguishes a venue that exists from a venue that runs the thing somebody wants. This read endpoint requires no authentication.
Places Referential
4- List Place Sports Retrieves the Sport Places referential of supported Decathlon sports, each with its ID, name, and the tags and filters allowed for that sport when describing an activity. Use it to discover which vocabulary can be applied to a given sport. This read endpoint requires no authentication.
- Get Place Sport Retrieves details for one sport from the Sport Places referential, including its English name and the tags and filters allowed for that sport. This read endpoint requires no authentication.
- Get Sport Allowed Filters Retrieves the list of filter names allowed for a specific sport in the Sport Places API. Filters carry a numeric or predefined string value describing an activity, such as distance, difficulty, or surface. This read endpoint requires no authentication.
- Get Sport Allowed Tags Retrieves the list of tag names allowed for a specific sport in the Sport Places API. Tags answer a yes or no question about an activity, such as whether lessons or equipment rental are offered. Pair with Get Sport Allowed Filters to validate a submission form before a user ever sees an error. This read endpoint requires no authentication.
Frequently Asked Questions
What can FlowRunner do with Decathlon?
FlowRunner agents can run List Sports, Get Sport, and Search Sports in Decathlon, plus 10 more actions.
Does connecting Decathlon to FlowRunner require OAuth?
No. Decathlon needs no credentials at all, so there is no key to obtain, store, or rotate.
Can Decathlon trigger a FlowRunner workflow automatically?
Decathlon doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Decathlon
$100 in credits. No card required. Connect in minutes.