Okapi Okapi

Fortnox API POST /api/bank-process-orders/v1/{id}/documents endpoint removal

Deprecated, no dateSubscribe to Fortnox APIShare

Fortnox deprecated the POST /api/bank-process-orders/v1/{id}/documents endpoint without a shutdown date. Calls made to this endpoint will fail.


Calls it hits

  • POST /api/bank-process-orders/v1/{id}/documents

What to use instead of these calls

Send the document with PUT /api/bank-process-orders/v1/{order_id}/documents instead.

In Fortnox API's words

This endpoint is deprecated. Use PUT /api/bank-process-orders/v1/{order_id}/documents instead.

Fortnox API, Announcement

Facts

API
Fortnox API api.fortnox.se
Kind
Endpoint removal
Takes effect
No date given yet
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Fortnox API's own pages

Questions

When does this change take effect?

Fortnox API deprecated POST /api/bank-process-orders/v1/{id}/documents without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Fortnox API has not given a shutdown date yet.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.


Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub

Get notifications

Subscribe to Fortnox API

Hear about each breaking change Fortnox API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Fortnox API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.