How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cadasto

Cadasto Query API

Management of [stored (registered) queries](https://specifications.openehr.org/releases/SM/latest/openehr_platform.html#_registered_queries) in the system.Actions upon resources of this group are also formally described in the [I_DEFINITION_QUERY](https://specifications.openehr.org/releases/SM/latest/openehr_platform.html#_i_definition_query_interface) Abstract Service Model interface.Stored queries are identified by their [qualified name and version](query.html#tag/Qualified_query_name).They can be executed using the [query endpoint](query.html#tag/Query/operation/query_execute_stored_query_body).

Documentation Provider Profile APIs.io OpenAPI GitHub

Cadasto Query API is one of 24 APIs that Cadasto publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Query. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 10 operations across 5 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version latest.

Requests are made against a single base URL, https://{baseUrl}/v1.

10 operations 5 paths 15 schemas 5 GET3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
latest
Base URL
https://{mycompany}.api.prod.cadasto.io/openehr/v1
Resource Areas
1

Paths & Operations 10

Across 5 paths, the API surfaces 10 operations — 5 GET, 3 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Query 10

Management of stored (registered) queries in the system. Actions upon resources of this group are also formally described in the IDEFINITIONQUERY Abstract Service Model interface.…

GET
/definition/query/{qualified_query_name}
List stored queries
definition_query_list 1 param → 200
PUT
/definition/query/{qualified_query_name}
Store a query
definition_query_store.yaml 2 params body → 200400
PUT
/definition/query/{qualified_query_name}/{version}
Store a query version
definition_query_version_store.yaml → 501
GET
/definition/query/{qualified_query_name}/{version}
Get stored query at version
definition_query_version_get 2 params → 200404
GET
/query/aql
Execute ad-hoc AQL
query_execute_adhoc_query 5 params → 200400408
POST
/query/aql
Execute ad-hoc AQL (POST)
query_execute_adhoc_query_body body → 200400408
GET
/query/{qualified_query_name}
Execute stored AQL
query_execute_stored_query 5 params → 200400404408
POST
/query/{qualified_query_name}
Execute stored AQL (POST)
query_execute_stored_query_body 1 param body → 200400404408
GET
/query/{qualified_query_name}/{version}
Execute stored AQL version
query_execute_stored_query_version 6 params → 200400404408
POST
/query/{qualified_query_name}/{version}
Execute stored AQL version (POST)
query_execute_stored_query_version_body 2 params body → 200400404408

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are ResultSetMetadata (6 properties), ResultSet (5 properties), StoredQuery (5 properties), AdhocQueryExecute (4 properties). Each schema is shown below with its type and property counts.

QueryType
string
Query formalism type.
QueryList
array
List of Stored Query resources.
StoredQuery
object
Stored Query content meta information.
5 properties 5 required
AQL
string
The given AQL query.
QueryVersion
string
The SEMVER version number of the Stored Query.
QueryName
string
The (fully qualified) name of the query (when is registered as a stored query), in a format of [{namespace}::]{query-name}. The namespace prefix is optional, a…
Offset
integer
The row number in result-set to start result-set from (0-based), default is 0.
ResultSet
object
5 properties 1 required
QueryParameters
object
A set of query parameters.
ResultSetMetadata
object
RESULTSET metadata.
6 properties
ResultSetColumn
object
An AQL column specification (e.g. a pair of column name and associated AQL path).
2 properties 1 required
AdhocQueryExecute
object
4 properties 1 required
Fetch
integer
Number of rows to fetch (the default depends on the implementation).
Query
object
3 properties 3 required
ResultSetRow
array
A set of cells representing a RESULTSET row, one cell for each column. Content of a cell is ANY (i.e. a OBJECT in most programming languages).

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cadasto-query-api-openapi.yml Raw ↑

Other APIs Cadasto publishes across the network.

openEHR Assistant MCP Server
AE Profile APIs.io
Cadasto ADL1.4 API
AE Profile APIs.io
Cadasto ADL2 API
AE Profile APIs.io
Cadasto Admin API
AE Profile APIs.io
Cadasto AGENT API
AE Profile APIs.io
Cadasto COMPOSITION API
AE Profile APIs.io
Cadasto CONTRIBUTION API
AE Profile APIs.io
Cadasto Datamap Definition API
AE Profile APIs.io
Cadasto Datamap Query API
AE Profile APIs.io
Cadasto DIRECTORY API
AE Profile APIs.io
Cadasto EHR API
AE Profile APIs.io
Cadasto EHR STATUS API
AE Profile APIs.io
#Query
← Back to C APIs
API Details
ID
cadasto:cadasto-query-api
Base URL
https://{mycompany}.api.prod.cadasto.io/openehr/v1
Docs
https://docs.cadasto.io/ehr-api
Provider
Cadasto
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cadasto-query-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cadasto-query-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Cadasto Query API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.