Skip to content

APIs

Every tool as an API

You can call every tool on the SuperCloud from your own software as well: calculate, convert, check and store. With one key, in one open language (IFCX), and you pay for what you use.

What a call looks like

A heat loss calculation from your own script: send an IFCX model and get the result per room back.

Illustrative example; the final specification will follow per tool.

curl -X POST https://demo.cloud.open-aec.eu/api/v1/heatloss/calculations \
  -H "Authorization: Bearer $OPENAEC_API_KEY" \
  -H "Content-Type: application/json" \
  --data @woning.ifcx

# antwoord
{
  "status": "done",
  "standard": "ISSO 51",
  "rooms": 12,
  "design_heat_loss_w": 6420,
  "result": "woning-warmteverlies.ifcx"
}

An API for every tool

26

Every tool gets an API. Availability follows that of the app.

How it works

  • Signing inAPI keys for scripts and integrations; OAuth for apps acting on behalf of a user.
  • SpecificationA public OpenAPI specification per tool, with examples.
  • LimitsLimits per key and per environment, so one script cannot overload your environment.
  • In the EUCalls are processed in the EU, with the same security as the apps themselves.

Sign up