Receiver proposal

Send a Finvoice ReceiverProposal message for Finnish e-invoice onboarding.

Send a Finvoice ReceiverProposal message to Ropo One via the REST API.

Ropo forwards the proposal to the debtor’s online bank.

The debtor approves it in their bank.

Prerequisites

• You have cid and apicode from Ropo support.

• You can fetch a JWT token. See Authentication.

Endpoints

• Production: https://ropo24.fi/rest/receiverproposal

• Test: https://rc.ropo24.fi/rest/receiverproposal

Token endpoint:

• Production: https://ropo24.fi/rest/token

• Test: https://rc.ropo24.fi/rest/token

Send a ReceiverProposal

Request

• Method: POST

• Header: Authorization: Bearer <token>

• Header: Content-Type: application/xml

• Optional header: Encoding: UTF-8 or Encoding: ISO-8859-1 Default is ISO-8859-1.

• Body: ReceiverProposal XML as a string (Finvoice standard).

Finvoice reference: https://www.finanssiala.fi/en/topics/finvoice-standard/

Example (curl)

ReceiverProposal.xml upload

# 1) Fetch token
TOKEN=$(
  curl -s -X POST "https://rc.ropo24.fi/rest/token" \
    -H "accept: application/json" \
    -H "content-type: application/json" \
    -d '{"cid":"<CID>","apicode":"<APICODE>"}' \
  | jq -r .token
)

# 2) Send ReceiverProposal XML
curl -X POST "https://rc.ropo24.fi/rest/receiverproposal" \
  -H "accept: application/json" \
  -H "authorization: Bearer $TOKEN" \
  -H "content-type: application/xml" \
  --data-binary "@/path/to/ReceiverProposal.xml"

Skip jq if needed.

Paste the token manually.

API reference

Add Receiver Proposals

post

Authorizations

bearerAuth

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Header parameters

EncodingstringOptional

Optional file encoding 'UTF-8' or 'ISO-8859-1'. Default encoding is 'iso-8859-1'

Body

application/xml

stringOptional

Responses

201

Successful operation

application/json

400

Bad request

application/json

401

Unauthorized

post

/receiverproposal

HTTPcURLJavaScriptPython

POST /rest/receiverproposal HTTP/1.1
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/xml
Accept: */*
Content-Length: 6

"text"

{
  "result": "success",
  "errors": "[['RP_uniqidT140443\\/1','Schema validation failed']]"
}