Explanatory Appendix API (v1)

Download OpenAPI specification:

Introduction

Explanatory Appendix API allows an agent to provide content for explanatory appendix. Explanatory appendix can be for following types of realties:

  • Residential share
  • Other share
  • Residential property
  • Estate property
  • Other property (includes also plot property)
  • Commercial property

Contact

If you have any questions, comments or feedback regarding our APIs, please contact developer@ovipro.fi.

Explanatory Appendix

Explanatory Appendix API allows you to create and manage explanatory appendixes. An explanatory appendix is specific to a single realty within an assignment.

Get an explanatory appendix

Gets the explanatory appendix data for given realty within an assignment.

Authorizations:
bearerAuth
path Parameters
assignmentId
required
string <uuid>
Example: 123e4567-e89b-12d3-a456-426614174000

The id of the assignment.

realtyId
required
string <uuid>
Example: 123e4567-e89b-12d3-a456-426614174001

The id of the realty.

header Parameters
Request-ID
required
string <uuid> ^([0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[8...
Example: 9031d1c5-7d40-41dd-b2b8-7919a2fc4fe9

A unique id which identifies the HTTP request. The value of this header must be created by the client. This identifier is used for troubleshooting purposes.

Responses

Response samples

Content type
application/json
Example
{
  • "assignmentId": "9238cf7b-b86a-49a5-b54f-cbdfcd03e9c9",
  • "realtyId": "9fd9124c-e6c1-4368-9f17-6938f0e2f524",
  • "categoryCode": "SALE",
  • "statusCode": "DRAFT",
  • "documentId": "123e4567-e89b-12d3-a456-426614174000",
  • "creationTime": "2022-12-31T13:00:00Z",
  • "modificationTime": "2022-12-31T13:00:00Z",
  • "realtyTypeCode": "RESIDENTIAL_SHARE",
  • "content": {
    }
}

Create an explanatory appendix

Creates a new explanatory appendix for given realty within an assignment.

Authorizations:
bearerAuth
path Parameters
assignmentId
required
string <uuid>
Example: 123e4567-e89b-12d3-a456-426614174000

The id of the assignment.

realtyId
required
string <uuid>
Example: 123e4567-e89b-12d3-a456-426614174001

The id of the realty.

header Parameters
Request-ID
required
string <uuid> ^([0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[8...
Example: 9031d1c5-7d40-41dd-b2b8-7919a2fc4fe9

A unique id which identifies the HTTP request. The value of this header must be created by the client. This identifier is used for troubleshooting purposes.

Request Body schema: application/json
required

Contains the explanatory appendix data.

realtyTypeCode
required
string (ResidentialShareRealtyTypeCode)

Determines the type of the realty and the data schema.

categoryCode
required
string (RealtyCategoryCode)
Enum: "SALE" "RENTAL"

Describes if the assignment and realty are for sale or rental.

required
object (ResidentialShareContent)

Responses

Request samples

Content type
application/json
Example
{
  • "realtyTypeCode": "RESIDENTIAL_SHARE",
  • "categoryCode": "SALE",
  • "content": {
    }
}

Response samples

Content type
application/json
{
  • "errorCode": "BAD_REQUEST_PARAMETERS",
  • "message": "Invalid request parameters",
  • "description": "Request parameters are missing or have invalid type.",
  • "errors": [
    ]
}

Update an explanatory appendix

Updates the explanatory appendix data for given realty within an assignment.

Authorizations:
bearerAuth
path Parameters
assignmentId
required
string <uuid>
Example: 123e4567-e89b-12d3-a456-426614174000

The id of the assignment.

realtyId
required
string <uuid>
Example: 123e4567-e89b-12d3-a456-426614174001

The id of the realty.

header Parameters
Request-ID
required
string <uuid> ^([0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[8...
Example: 9031d1c5-7d40-41dd-b2b8-7919a2fc4fe9

A unique id which identifies the HTTP request. The value of this header must be created by the client. This identifier is used for troubleshooting purposes.

Request Body schema: application/json
required

Contains the updated explanatory appendix data.

One of
required
object (ResidentialShareContent)

Responses

Request samples

Content type
application/json
Example
{
  • "content": {
    }
}

Response samples

Content type
application/json
{
  • "errorCode": "BAD_REQUEST_PARAMETERS",
  • "message": "Invalid request parameters",
  • "description": "Request parameters are missing or have invalid type.",
  • "errors": [
    ]
}

Execute an explanatory appendix action

Executes an explanatory appendix action.

Authorizations:
bearerAuth
path Parameters
assignmentId
required
string <uuid>
Example: 123e4567-e89b-12d3-a456-426614174000

The id of the assignment.

realtyId
required
string <uuid>
Example: 123e4567-e89b-12d3-a456-426614174001

The id of the realty.

header Parameters
Request-ID
required
string <uuid> ^([0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[8...
Example: 9031d1c5-7d40-41dd-b2b8-7919a2fc4fe9

A unique id which identifies the HTTP request. The value of this header must be created by the client. This identifier is used for troubleshooting purposes.

Request Body schema: application/json
required

Contains the explanatory appendix action data.

actionCode
required
string
Enum: "LOCK" "UNLOCK" "APPROVE"

The action to be performed on the explanatory appendix. Possible values are:

  • LOCK: Generates explanatory appendix PDF document and sets the status to READY_FOR_SIGNING. Only available if the explanatory appendix is in DRAFT state.
  • UNLOCK: Sets the status to DRAFT. Only available if the explanatory appendix is in READY_FOR_SIGNING state.
  • APPROVE: Sets the status to APPROVED. Only available if the explanatory appendix is in READY_FOR_SIGNING state.

Responses

Request samples

Content type
application/json
{
  • "actionCode": "LOCK"
}

Response samples

Content type
application/json
{
  • "errorCode": "BAD_REQUEST_PARAMETERS",
  • "message": "Invalid request parameters",
  • "description": "Request parameters are missing or have invalid type.",
  • "errors": [
    ]
}

Import explanatory appendix from another system

Imports explanatory appendix from another system. The imported explanatory appendix must be signed by the assignee and the ID of the signed document must be provided in the request body. The explanatory appendix will be created into APPROVED state. The actual content of the explanatory appendix is not needed and cannot be provided in a structured format. A specific permission is required to use this endpoint.

Authorizations:
bearerAuth
path Parameters
assignmentId
required
string <uuid>
Example: 123e4567-e89b-12d3-a456-426614174000

The id of the assignment.

realtyId
required
string <uuid>
Example: 123e4567-e89b-12d3-a456-426614174001

The id of the realty.

header Parameters
Request-ID
required
string <uuid> ^([0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[8...
Example: 9031d1c5-7d40-41dd-b2b8-7919a2fc4fe9

A unique id which identifies the HTTP request. The value of this header must be created by the client. This identifier is used for troubleshooting purposes.

Request Body schema: application/json
required

Contains the explanatory appendix data.

realtyTypeCode
required
string (RealtyTypeCode)
Enum: "RESIDENTIAL_SHARE" "OTHER_SHARE" "RESIDENTIAL_PROPERTY" "ESTATE_PROPERTY" "COMMERCIAL_PROPERTY" "OTHER_PROPERTY"

Describes the type of the realty in terms of used endpoint. Possible values are:

  • RESIDENTIAL_SHARE is a share type of realty meant for living.
  • OTHER_SHARE is any other share type of realty.
  • RESIDENTIAL_PROPERTY is a property type of realty meant for living.
  • ESTATE_PROPERTY is a large area of land that can include buildings.
  • COMMERCIAL_PROPERTY is commercial property type of realty.
  • OTHER_PROPERTY is any other property type of realty.
categoryCode
required
string (RealtyCategoryCode)
Enum: "SALE" "RENTAL"

Describes if the assignment and realty are for sale or rental.

documentId
required
string

The id of the signed explanatory appendix document.

Responses

Request samples

Content type
application/json
{
  • "realtyTypeCode": "RESIDENTIAL_SHARE",
  • "categoryCode": "SALE",
  • "documentId": "123e4567-e89b-12d3-a456-426614174000"
}

Response samples

Content type
application/json
{
  • "errorCode": "BAD_REQUEST_PARAMETERS",
  • "message": "Invalid request parameters",
  • "description": "Request parameters are missing or have invalid type.",
  • "errors": [
    ]
}