- Arm yourself with an HTTP client (e.g. curl, your own client code, or even this browser) and you’re good to go.
curl https://data.mksmart.org/entity/If the response is JSON content of the type
"subresources": [ ... ],
"comment": "Beware: I live!",
Exploring by type and identifierMaking requests to the entity-centric API is relatively simple, as long as you know the type and identifier of the entity about which information is required. For example, getting information about the geographic sector “MK77” is simply done by calling the URI:
MK77here is the identifier of the entity to be retrieved. The format of the identifier is dependent on the type. A
postcodefor example might rather be
topicare identified by their name (e.g.
computer), while a
geo-pointis identified by its coordinate (e.g.
The following interactive API specification allows you to try out calls to the MK:Smart entity API right before you add them to your development environment. Click on the list items below to see the supported operations and parameters. Powered by Swagger.
Response formatAll the services return bespoke, simple JSON, aggregating information from multiple sources. The result of calls such as the ones of the examples above will return a simple JSON object with attributes coming from the original sources.
"sub-property1": ["value1", "value2", ...],
"sub-property2": ["value3", "value4", ...].