Company rest API

Association register - document query

The API returns an association register document in JSON format, as specified by association register number.

In order to use the API you must have the valid environment-specific username and password. Before any API requests, you need to obtain an API KEY. You will get a valid API KEY (it's called a ticket) by using the ticket API (Please, read how to use ticket API instructions).

The API KEY must be sent in the request custom header element (named ticket or x-api-key). If the API KEY value is valid then API request will be successful (http status code 200), otherwise it will fail (http status code 401). All API requests must be made over HTTPS. Request the username and password

API endpoints

  • - production environment
  • - test environment

API request parameters

registry number Association register number X

API response

status Current status of the association
rekisterinumero Association register number
otteen_tyyppi Document type
ote_ajalta Document period
oteteksti Document text

API request and response example

curl '' -H 'ticket: 592040XBBE21E9265DCA9526B59F5C960682521A254CAD5'

Request succeeded with given parameters. API responded in JSON format.

    "status": "OK",
    "rekisterinumero": "28.807",
    "otteen_tyyppi": "voimassaoleva",
    "ote_ajalta": "29.05.2014",
    "oteteksti": "NAMN\nBorgå Simmare - Porvoon Uimarit r.f.\n\nHEMORT\nBorgå\n\nADRESS\nLinnankoskenkatu   2-6\n06100 Borgå\n\n\nREGISTERNUMMER\n28.807\n\n",
    "Error": null


Please note that data coverage varies between companies. Data coverage depends e.g. on company form. Remember the codes and descriptions API returns all companies REST APIs code values and descriptions - read more.