Current information for our partners

2026-10-20

From 30 April 2027, Kivra will introduce new validations and validate content sent through the API, to give recipients a better experience and make sendouts more secure. Content that doesn’t pass validation will be rejected. You can test in the sandbox from 1 February 2027. We’ve also introduced new error codes as of 21 october 2026.

What’s changing

• Validation against the technical specification. Content that doesn’t follow the specification is rejected. This includes fields that aren’t part of the specification.
• New validations. For example, PDF files must be valid, the MIME type must be correct and each content can only have one recipient identifier. All new validations are listed below.
• Clearer error responses. When content is rejected, the response shows which fields are wrong and why. Several error codes are grouped under one common error code. Review error codes.

What do you need to do?

• Check that your content follow the specification
• Adjust your content to the new validations
• Update any internal logic that relies on the current response codes
• Test in the sandbox from 1 February 2027

Validated for all content types

• PDF is mandatory and must be a valid PDF file. Don’t send Word, XML or image files. We recommend PDF/A.
• The declared MIME type must match the file’s actual type. If a part is declared as PDF, we check that the file is a real PDF. Otherwise, the content is rejected for security reasons.
• subject must be included and can’t be null or an empty string.
• Fields that aren’t free text can’t have leading or trailing spaces. Example: “letter “ is not accepted, “letter” is.
• content type must be written in lowercase. Example: invoice.reminder is accepted, Invoice.Reminder is rejected.
• Content with unknown metadata fields is rejected. This keeps personal data or other information from reaching us by mistake.
• Responsive content can’t use scripts of any kind. All resources in the responsive HTML document, such as images or fonts, need to be embedded in the document.
• Only one recipient identifier per content. Send either a personal identity number or an email address.
• Don’t send campaign_tag if the content isn’t part of a campaign.

Validated for invoices Applies to invoice, invoice.reminder, invoice.renewal, invoice.debtcollection, invoice.debtcampaign, invoice.paymentnotice and invoice.donation.

• All invoice types require payment metadata.
• due_date must be in the future when Kivra receives the content. Applies to invoice, invoice.renewal and invoice.paymentnotice.

Validated when sending on behalf of someone else (behalf_of)

If you send behalf_of, vat_number must be a valid Swedish VAT number. It consists of SE, the organisation number and 01, 14 characters in total, for example SE556677889901. Applies to letter.signed, invite.research, invite.gift, invite.sign, invite.voucher and invite.kyc.

API changes

• generated_at is being removed.
• payment_multiple_options.status is no longer accepted.

New and optional

• You can specify payment method in plain text, for example bankgiro or bg and plusgiro or pg.
• A new optional field lets you exclude a single invoice from Autogiro, even if the recipient has Autogiro activated.

2026-10-14

Your senders can now send invoices with structured data alongside the PDF to small and medium-sized businesses. The recipient’s accounting system reads the details directly instead of interpreting a PDF, which means fewer errors and faster handling. This applies to recipients who have connected Kivra Business to their accounting system. Fortnox is first, and more systems are on the way.

What do you need to do? You need to build support for the content type accounting.invoice in our API for sending content. It works like a regular invoice, but with more metadata. Select the example “accounting invoice to company” in the dropdown in the documentation to see the structure. Read more here on our developer pages. Contact our partner team if you want to get started.

2025-08-27

Following the introduction of new services, we have updated the Service Description and Special Terms with corresponding changes to our personal data processing. We have made only editorial changes to the security annex. All of these updates apply to both your partner agreement package and the agreement package for senders who transmit via partners.

In your partner agreement package, we have also updated the Service Level Agreement to include the new service Recommended E-Deliveries and to clarify the process for troubleshooting.

The updated documents are listed below:

Updated documents for Partners:

• Tjänstebeskrivning och Särskilda Villkor
• Underbilaga A Specifikation till Underbiträdesavtal
• Underbilaga B Säkerhet till Underbiträdesavtal
• Servicenivåavtal

Updated documents for Senders who transmit via Partners:

• Tjänstebeskrivning och Särskilda Villkor
• Underbilaga A Specifikation till Personuppgiftsbiträdesavtal
• Underbilaga B Säkerhet till Personuppgiftsbiträdesavtal

The changes are effective immediately.

2025-05-05

Now, partners can register for webhooks by contacting our Sender Success. With webhooks, a call will be made when new content arrives in one of your customers' company inboxes, so that you no longer need to "poll" an inbox for new content. Read more here on our developer pages.

2024-11-19

Starting April 30, 2025, Kivra will discontinue version 1 of Usermatch in our matching service.

Moving to v2 of Usermatch offers several advantages for you as an integrating partner. With Usermatch v2 you can match users against a verified email address and also companies against VAT number (VAT), in addition to matching on personnummer (SSN).

What do you need to do? Here are the two steps to go from v1 to v2:

1 Change the URL from /v1/tenant/{tenantKey}/usermatch to:

• /v2/tenant/{tenantKey}/usermatch/ssn
• /v2/tenant/{tenantKey}/usermatch/verified_email
• /v2/tenant/{tenantKey}/companymatch/vatnr 2 Change SSNs to LIST in the metadata for both request and response.

2024-11-01

We've made it even easier for you as a partner to integrate with Kivra Företag, which is used by over 175,000 companies. With the new integration, your customers can easily sign up for Kivra Företag directly within your system, and the integration is activated automatically. Your customers can then read and manage all their company mail – government letters and other important documents – directly within your system. This saves both time and hassle!

Want to learn more about how to integrate your system with Kivra Företag and the possibilities with a customized onboarding process for company mailboxes? Contact adrian.fickler(at)kivra.com!

2024-03-05

We have made it even easier for you as partner. From now on, you can use our user-match functionality for companies and organizations as well, i.e. when you match with an an organizational number.

More details here

2023-11-28

Vi vill uppmärksamma er på att Kivra kommer införa 3 viktiga förändringar i sender API, enligt nedan.

1. 31a maj 2024 kommer vi stänga v1/tenant/TENANT_ID/content och ber alla som är integrerade mot Kivras API att istället använda v2/tenant/TENANT_ID/content
2. I och med övergången till v2 blir attributen type and subject obligatoriska i metadatastrukturen för v2/tenant/TENANT ID/content
3. Vi tar bort [payment] metadatastrukturen. Dess funktionalitet kommer att ersättas med den redan existerande [payment_multiple_options] metadatastrukturen

Exempel av betalning i v1 och v2 av content endpoint

To ensure that you, as a partner, send correctly and always have support for our new and upcoming services, we recommend planning a transition to Kivra's Content API v2.

We have launched version 2 of our API, and to this version, we have transferred the following features:

• Responsive Design: Customize content based on the device it's displayed on. With HTML, we enable features like graphs, charts, dropdown menus, and carousels - a more sophisticated layout, in essence.
  
• Forms: Create and send forms through our 'Forms' API and collect valuable information from users.
  
• Email Matching: We now allow matching Kivra users based on email addresses, not just personal identification numbers as before.
  
• Campaigns by Tag: The ability to target campaigns based on your sender's own segmentation.
  This change was made due to limitations in v1's metadata structure. API v2 has a flatter and more flexible structure, making it easier to develop and enhance our services.
  
  Currently, the above four services have already transitioned to API v2. Other services will gradually move from V1 to V2.

2023-09-05

The option to add a Campaign tag when sending content through our API is now available in beta version. The sender needs to activate a new metadata field to enable the use of a Campaign tag.

The campaign is created by adding a tag in 'Campaigns'. When content is sent through Kivra's content-API and a tag is added to the new metadata field, Kivra links the campaign if there's a match. This tag segmentation will then replace all other options in 'Campaigns'.

For more information, contact us.

2021-09-07

Batchintegrationen stängs ner 31 december 2022

Kivra har tagit beslut om att stänga ner all vår batch-integration. Det innebär att det – om en tid – inte längre kommer vara möjligt att exempelvis hämta user accept-filer eller skicka in filer till oss.

Varför görs förändringen?

Vi gör förändringen för att vi tillsammans med våra partners ska kunna introducera nya tjänster och funktionalitet som kräver realtidsinteraktion. Batch-lösningen är inte optimerad för det. Däremot stödjer Kivras API-tjänst nya funktioner till fullo.

Vad innebär det för partners?

För er som partner innebär det att ni behöver se över och förändra hela eller delar av er intergrationsuppsättning och istället övergå till vår API-tjänst. Vi förstår att det innebär extra arbete för er. Därför har vi satt en väl tilltagen deadline – 31 december, 2022.

Mer om förändringen

Det finns fler skäl till att vi överger batch-lösningen. Det primära att vi ökat vår utvecklingstakt på Kivra och flera betydande funktioner har inte fullt stöd i den äldre lösningen. En stor del av vår partner- och kundbas har redan gjort skiftet och vi vill såklart att ni ska ha samma förutsättningar att ta del av hela vårt produktutbud.

Frågor och plan för migrering?

Vi kommer vara behjälpliga med stöd för tekniska frågor under övergången. Vi bistår också gärna med en plan för er att migrera från batchlösningen till API-tjänsten. Frågor om övergången besvaras av er Partneransvarige. Ni hittar kontaktuppgifter till supporten längst ner på denna sida om ni behöver hjälp med att integrera via Kivras API.

As announced already one year ago via kivrastatus.se and mail (https://kivrastatus.se/details/b01e178293096) partners and senders should use the following API endpoints to communicate via Kivra:

• Production environment: sender.api.kivra.com (instead of api.kivra.com)
• Sandbox environment: sender.sandbox-api.kivra.com (instead of sandbox.kivra.com).

Partners and senders that have not updated the endpoint yet are required to proceed with the change as quickly as possible and no later than 31st October 2021.

For questions please contact partner@kivra.com or paolo.leva@kivra.com

For questions about how to integrate via our API, contact us here.