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

University of Helsinki Forms API

The Forms API from University of Helsinki — 4 operation(s) for forms.

University of Helsinki Forms API is one of 97 APIs that University of Helsinki publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 11 JSON Schema definitions.

Tagged areas include Forms. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and 11 JSON Schemas.

This API exposes 7 operations across 4 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://api.laji.fi.

7 operations 4 paths 32 schemas 1 DELETE3 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.helsinki.fi/portal/environments/DEFAULT
Authentication
HTTP Bearer, API Key, API Key
Resource Areas
1

Authentication & Security 3

University of Helsinki Forms API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Access_token). An API key is passed in the header as Accept-Language (Lang). An API key is passed in the header as Person-Token (Person_token).

  • Access_token — Access token
  • Lang — Sets the 'Accept-Language' header. One of 'fi', 'sv,' 'en'. Defaults to 'en'.

Paths & Operations 7

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

Forms 7
GET
/forms/{id}/participants
Get participants of a form. Only for form admins
FormsController_getParticipants 2 params → 200400401403404406422500
GET
/forms
Get a page of forms
FormsController_getListing → 200400401403404406422500
POST
/forms
Create a new form
FormsController_create body → 201400401403404406422500
GET
/forms/{id}
Get a form by id
FormsController_getOne 3 params → 200400401403404406422500
PUT
/forms/{id}
Update an existing form
FormsController_update 1 param body → 200400401403404406422500
DELETE
/forms/{id}
Delete a form
FormsController_remove 1 param → 200400401403404406422500
POST
/forms/transform
Get preview of form transformed from json format to schema format
FormsController_transform body → 201400401403404406422500

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are store-unit (119 properties), store-gatheringFact (103 properties), store-gathering (98 properties), store-document (79 properties). Each schema is shown below with its type and property counts.

store-form
object
21 properties 21 required
store-unit
object
119 properties 119 required
store-gatheringFact
object
103 properties 103 required
store-gatheringEvent
object
39 properties 39 required
store-formFooter
object
5 properties 5 required
store-unitGathering
object
8 properties 8 required
store-contact
object
11 properties 11 required
store-measurement
object
27 properties 27 required
Participant
object
7 properties 7 required
store-typeSpecimen
object
17 properties 17 required
store-formOptions
object
62 properties 61 required
store-completeList
object
5 properties 5 required
store-lineTransectNest
object
10 properties 10 required
Form
object
25 properties 25 required
JSONSchemaPrimitive
object
2 properties 2 required
JSONSchemaObject
object
3 properties 3 required
store-identification
object
29 properties 29 required
store-document
object
79 properties 1 required
store-unitFact
object
47 properties 47 required
store-field
object
15 properties 15 required
FormListing
object
10 properties 10 required
store-sample
object
33 properties 1 required
store-documentIdentification
object
5 properties 5 required
JSONSchemaArray
object
6 properties 2 required
store-multiLang
string
store-preparation
object
9 properties 9 required
store-formNamedPlaceOptions
object
49 properties 49 required
store-taxonCensus
object
6 properties 1 required
store-geometry
JSONSchema
store-gathering
object
98 properties 98 required
store-formSeason
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-helsinki-forms-api-openapi.yml Raw ↑

Other APIs University of Helsinki publishes across the network.

University of Helsinki API Portal (Gravitee)
Dependency Track
Flamma Liferay Headless API
Internal Guide CMS JSON-API
Helda DSpace REST API
Helda OAI-PMH Metadata Interface
HY Data Catalogue DSpace REST API
HY Data Catalogue OAI-PMH Interface
Editori (journals.helsinki.fi) OAI-PMH Interface
HY Login Service — Shibboleth IdP + OpenID Connect
Sisu (Kori) Student Information System — University of Helsinki tenant
University of Helsinki Research Portal — Elsevier Pure tenant
Where this information came from

This is an independent, third-party profile of University of Helsinki Forms 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.