Hello everyone, and welcome back to those returning from vacation! We hope Christmas and New Years were a blast. 🎆 Time to get back in the game — here’s what’s new in our API.


🆕Added




🐛Fixed

  • $filter now supports ltand gt for the property PaymentStatus on /v2/customerinvoices.
    • The existing $filterparameter for GET /v2/customerinvoices can now handle "less than" (lt) and "greater than" (gt) when filtering by PaymentStatus.


As always, if you have questions, or feedback, let us know. API Support 📬.

Hello! 🎄

Christmas came early this year, and we have a gift for you.

We are very thrilled to announce that our platform change is now complete! 🎉

Over the last couple of months, we have been working hard to elevate our External API to the next level, with both a new .NET version as the code engine and a brand-new documentation page. In short, this means that from now on, you will find our API documentation at this page: Spiris Bookkeeping & Invoicing/eAccounting API Documentation (based on Scalar


A few upsides:

  • Faster loading times
    • Optimised rendering and smaller bundle size
  • Smooth scrolling and navigation
    • Improved performance for large specification files
  • API versioning support
    • Better handling of multiple API versions
  • Improved search functionality
    • Faster and more accurate API endpoint discovery
  • Clean and intuitive interface
    • More polished and user-friendly design
  • Better visual hierarchy
    • Easier to navigate and find information
  • Responsive design
    • Works seamlessly across desktop, tablets, and mobile devices

The main advantage is that Scalar provides a more modern, performant, and user-friendly way to present the same OpenAPI specifications that Swagger UI uses, without requiring changes to your existing API documentation workflow.

What do you think? Don’t hesitate to reach out to us with feedback ➡️ Support. 📫

🆕 Added


💀 Deprecated

  • Swagger, as the old API Documentation page.

Pumpkin spice greetings! 🍂 Autumn's here, and so are our new releases!

Changes

Over the next couple of weeks, we will update the format of URL links for some of our endpoints.
Old format: https://apistorage.vismaonline.com/v3/temp/fileanonymous/{FILE_GUID}
New format: https://eaccountingstorage{countryCode}.vismaonline.com/temp/fileanonymous/{FILE_GUID}


🆕 Added

  • New property for CompanySettingsApi. Affected endpoints: GET /v2/CompanySettings, PUT /v2/CompanySettings
    • DefaultBackgroundId - default company background to be used on printed sales documents. Used for Swedish and Dutch companies only.

As always, if you have any questions regarding this or other matters, let us know. API support.

Hello everyone, and welcome back to those returning from vacation! We hope summer treated you well. ☀️
Time to get back in the game — here’s what’s new in our API.

🆕 Added


🐛 Fixed

Error handling for order drafts:

  • GET /v2/orders/{id}/print now returns a ValidationException with the message "Order drafts cannot be printed", when called for an order draft.
  • POST /v2/orders/{id}/email now returns a ValidationException with the message "Order drafts cannot be sent by e-mail", when called for an order draft.

Any questions? You know what to do ➡️ Support. 📫

Hey dev peeps! 🍀

Summer is here, and so are the new updates in our API. Let's dive in!

🆕 Added

  • New endpoint: GET /v2/backgrounds. This endpoint lets you get all available document backgrounds.

  • New property for DocumentApi. Affected endpoint: GET /v2/documents/{id}.
    • Title - Represents the title or descriptive name of the document.





As always, if there're any questions, don't hesitate to reach out. Support 📫.

We're excited to announce that Visma Spcs is now Spiris.
This also means a small change in product naming:

  • In Sweden, Visma eEkonomi is now called Bokföring & Fakturering/Bookkeeping & Invoicing.
  • In all other markets, the product name remains eAccounting.

Our API continues to support integrations across borders, and these naming updates will not affect your existing setups.

Read more about this here.
If you have any questions, don’t hesitate to reach out. We're here to help.

Hello, dev people! 👋
Just stopping by with a few new updates. No brand new endpoints this time – but, we've given the old ones some well-deserved attention. Here's what's new:

🆕Added


  • New error messages now visable.
    We've added a few error messages to the documentation that were already in use behind the scenes. Now they're properly listed, so you'll know exactly what to expect if things go sideways. You can find them here.


As always, let us know if anything looks funky or if you've got questions. Until next time – happy coding! 💻

Howdy, code wranglers! 🤠
Spring is in the air, and we've got some fresh updates for you. Let's get down to business:

🆕Added

  • New property for AttachmentResultApi. Affected endpoint GET /v2/attachments, GET /v2/attachments/{attachmentId}

    • Photosource
      • Unknown = 0
      • VismaScannerApp = 1
      • CompanyEmail = 2
      • EmployeeEmail = 3
      • DragAndDrop = 100
      • eInvoice = 101
      • ScanPDF = 102
      • ScanLetter = 103
      • Integration = 105
  • Four new properties for CompanySettingsApi. Affected endpoint GET /v2/companysettings, PUT /v2/companysettings

    • UsesSupplierInvoiceEdit - Allow editing of purchase invoices.
    • UsesAdvancedMode - Show debit and credit on purchase invoices.
    • FirstPaymentReminderWithoutFee - Describes if first payment reminder is free of charge. To skip updating this property, set it to null.
    • LatePaymentFee - Late payment fee. To skip updating this property, set it to null.

As always, if there are any questions, just toss them our way and let's tackle them together. Happy coding, everyone! 🌞

Hey developers! We've got some exciting updates for you:

🆕 Added

Time to integrate and make your applications even more powerful! Happy coding! 😎

Payroll API news

by Emelie Gasslander

Greetings, developers! 🧑‍💻
We've got some new and shiny updates for you. Let's dive right into the details:

🆕 Added

New property for CreateEmployeeContractRequest. Affected endpoint: POST /v2/employees

  • TimeReserveType - Timebank reserve type
    • 1 = WorkingTimeReserve
    • 2 = WorkingTimeAcount

New properties for CreateEmployeeResponse and EmployeeResponse. Affected endpoints: POST /v2/employees, GET /v2/employees, GET /v2/employees/{employeeId}

  • TimeResereveType - Timebank reserve type
    • 1 = WorkingTimeReserve
    • 2 = WorkingTimeAcount
  • TimeResereveInMinutes - Amount of minutes accumulated in timebank reserve

New property for CreateTimebankRequest and TimebankUpdateRequest. Affected endpoints: POST /v2/shortcuts/timebank, PUT /v2/shortcuts/timebank/{id}

  • PayOutSource - Type of hours balance, which will be decreased by the shortcut
  • 1 = CompensationTime
  • 2 = WorkingTimeReserve
  • null will be interpreted as CompensationTime

New property for TimebankResponse. Affected endpoints: POST /v2/shortcuts/timebank , GET /v2/shortcuts/timebank/{timebankId} , GET /v2/shortcuts/timebank/{startDate}/{endDate} , PUT /v2/shortcuts/timebank/{id}

  • PayOutSource - Type of hours balance, which will be decreased by the shortcut
    • 1 = CompensationTime
    • 2 = WorkingTimeReserve

💀 Deprecated

Deprecated properties for CreateTimebankRequest and TimebankUpdateRequest. Affected endpoints: POST /v2/shortcuts/timebank , PUT /v2/shortcuts/timebank/{id}

  • ScheduleStartTime - Deprecated (value will be ignored)
  • ScheduleEndTime - Deprecated (value will be ignored)
  • ScheduledDayBreakTime - Deprecated (value will be ignored)

Deprecated properties for TimebankResponse Affected endpoints: POST /v2/shortcuts/timebank , GET /v2/shortcuts/timebank/{timebankId} , GET /v2/shortcuts/timebank/{startDate}/{endDate} , PUT /v2/shortcuts/timebank/{id}\

  • ScheduleStartTime - Deprecated (value will always be null)
  • ScheduleEndTime - Deprecated (value will always be null)
  • ScheduledDayBreakTime - Deprecated (value will always be 0)

Happy coding! If you have any more questions or need further clarification, feel free to ask. Support 📧