1. Operations
Confirma Finance Integrations API
  • Introduction
  • Authentication
  • Environments
  • Data validation
  • Contact information
  • Go Live & Deployment Guide
  • Services
    • Services
    • Invoice Intermediation service
    • Invoice Lifecycle service
    • Debt Collection services
    • Accounting integrations
    • Print and Distribution service
      • Overview
    • Operations
      • Overview
  • Core endpoints
    • Onboarding
      • Introduction to onboarding
      • Create a new client
      • Validate access token
      • Renew access token
    • Invoices
      • Introduction to Invoices
      • Create an invoice
      • Create an Invoice Action
      • Retrieve case details
      • Retrieve distribution Information
      • Retrieve distribution Information MV v2
    • Payments
      • Introduction to Payments
      • Retrieve Payments
      • Retrieve settlements
    • Accounting
      • Introduction to accounting
      • Invoice
        • Invoice
      • Ledger
        • Ledger
        • Ledger
      • Payment
        • Payment
        • Payment
    • Operations
      • Retrieve Finvoice Credentials
  • Schemas
    • Finvoice Credentials Response
    • Invoice Header object
    • Invoice Parties
    • Invoice Attachments
    • InvoiceExtensions
    • Client Settings
    • Accounting
    • Address
    • BuyerParty
    • Collection
    • Collection Costs
    • Collection Interest
    • Contact
    • Contact Person
    • Definition Detail
    • Delivery Party
    • Distribution
    • Factoring
    • Interest
    • InvoiceAmounts
    • Invoice Content Data
    • Invoice Recipient Party
    • InvoiceReferences
    • InvoiceRowData
    • InvoiceTerms
    • PaymentData
    • Payment Details
    • PaymentState
    • PaymentTerms
    • Processing
    • SalesInvoiceRequest
    • Seller Party
Need help?
  1. Operations

Overview

This page contains additional helpful endpoints for the partner to implement.

Retrieve Finvoice Credentials#

This endpoint retrieves electronic invoicing (Finvoice) registry information for a Finnish company using its Business ID (Y-tunnus). The data is sourced from the national Finvoice registry and returns the e-invoicing addresses and operator details that the specified business has registered for receiving electronic invoices.
📌
This endpoint is provided at no additional cost to all users.
The service is optimized for low-latency responses and is suitable for real-time use cases.

How it works#

When a valid Business ID is provided, the service queries the Finvoice registry and returns all matching e-invoicing address records associated with that company.
A single company may have:
Multiple e-invoice addresses
Multiple operators
Different address types for different invoicing channels
Because of this, the response is always returned as an array of records, even if only one record exists.

Response structure#

Each item in the response represents one registered e-invoicing address and includes:
eInvoiceAddressName – Name of the recipient organization as registered
eInvoiceAddress – The electronic invoicing address (e.g., EDI or IBAN-based identifier)
eInvoiceAddressType – Code defining the address format/type (e.g., EDI, IBAN)
eInvoiceOperatorId – Identifier of the e-invoicing operator
eInvoiceOperatorName – Name of the operator providing the e-invoicing service
lastModified – Timestamp of when the record was last updated in the registry

Client responsibility#

The API does not determine which e-invoicing address should be used.
If multiple records are returned, the client application is responsible for:
Selecting the appropriate e-invoicing address
Applying any business rules or user preferences
Presenting options to end users when necessary
Notes
The endpoint is read-only and reflects the current state of the Finvoice registry. Data availability depends on the registry; not all businesses have registered e-invoicing details. An empty array indicates that no e-invoicing information was found for the given Business ID
Previous
Overview
Next
Introduction to onboarding
Built with