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
University of Helsinki

University of Helsinki Named places API

The Named places API from University of Helsinki — 3 operation(s) for named places.

Documentation Provider Profile APIs.io OpenAPI GitHub

University of Helsinki Named places 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 Named places. 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 3 paths, and defines 22 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 3 paths 22 schemas 2 DELETE2 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 Named places 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 3 paths, the API surfaces 7 operations — 2 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Named places 7
POST
/named-places/{id}/reservation
Reserve an existing named place
NamedPlacesController_reserve 4 params → 201400401403404406422500
DELETE
/named-places/{id}/reservation
Cancel a reservation for a named place
NamedPlacesController_cancelReservation 2 params → 200400401403404406422500
GET
/named-places
Get a page of named places
NamedPlacesController_getPage 12 params → 200400401403404406422500
POST
/named-places
Create a new named place
NamedPlacesController_create 1 param body → 201400401403404406422500
GET
/named-places/{id}
Get a named place by id
NamedPlacesController_get 2 params → 200400401403404406422500
PUT
/named-places/{id}
Update an existing named place
NamedPlacesController_update 2 params body → 200400401403404406422500
DELETE
/named-places/{id}
Delete a named place
NamedPlacesController_delete 2 params → 200400401403404406422500

Schemas 22

The contract defines 22 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-unit
object
119 properties 119 required
store-gatheringFact
object
103 properties 103 required
store-gatheringEvent
object
39 properties 39 required
store-unitGathering
object
8 properties 8 required
store-contact
object
11 properties 11 required
store-measurement
object
27 properties 27 required
store-dateRange
object
5 properties 5 required
store-typeSpecimen
object
17 properties 17 required
store-completeList
object
5 properties 5 required
StoreDeleteResponse
object
1 property 1 required
store-lineTransectNest
object
10 properties 10 required
store-identification
object
29 properties 29 required
store-document
object
79 properties 1 required
store-unitFact
object
47 properties 47 required
store-reserve
object
5 properties 2 required
store-namedPlace
object
27 properties 2 required
store-sample
object
33 properties 1 required
store-documentIdentification
object
5 properties 5 required
store-preparation
object
9 properties 9 required
store-geometry
store-taxonCensus
object
6 properties 1 required
store-gathering
object
98 properties 98 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-helsinki-named-places-api-openapi.yml Raw ↑

Other APIs University of Helsinki publishes across the network.

University of Helsinki API Portal (Gravitee)
AE Profile APIs.io
Dependency Track
AE Profile APIs.io
Flamma Liferay Headless API
AE Profile APIs.io
Internal Guide CMS JSON-API
AE Profile APIs.io
Helda DSpace REST API
AE Profile APIs.io
Helda OAI-PMH Metadata Interface
AE Profile APIs.io
HY Data Catalogue DSpace REST API
AE Profile APIs.io
HY Data Catalogue OAI-PMH Interface
AE Profile APIs.io
Editori (journals.helsinki.fi) OAI-PMH Interface
AE Profile APIs.io
HY Login Service — Shibboleth IdP + OpenID Connect
AE Profile APIs.io
Sisu (Kori) Student Information System — University of Helsinki tenant
AE Profile APIs.io
University of Helsinki Research Portal — Elsevier Pure tenant
AE Profile APIs.io
#Named places
← Back to U APIs
API Details
ID
university-of-helsinki:university-of-helsinki-named-places-api
Base URL
https://api.helsinki.fi/portal/environments/DEFAULT
Docs
https://api.helsinki.fi/portal/
Provider
University of Helsinki
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=university-of-helsinki-named-places-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/university-of-helsinki-named-places-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 University of Helsinki Named places 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.