Skip to content

SOAP nuance #95

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ezw2000 merged 2 commits into from
Nov 25, 2025
Merged

SOAP nuance #95

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
928b46d
SOAP nuance
ezw2000 Nov 24, 2025
cc66f95
Nog duidelijker voor SOAP lezers
ezw2000 Nov 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Empty file added markdownpages/profit/en/news-profit6
View file
Open in desktop
Empty file.
25 changes: 17 additions & 8 deletions markdownpages/profit/en/news-profit7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
author: EZW
date: 2025-11-10
date: 2025-11-25
tags: Profit7, GetConnector, UpdateConnector, Integration, Configuration
title: New in Profit 7
---
Expand All @@ -11,19 +11,28 @@ Starting with Profit 7, several changes have been implemented in the AFAS Profit

## **Breaking changes**

### Always send AFAS-token base64-encoded
### Always send AFAS token base64-encoded

As already announced in the [new in Profit 6](news-profit6/#afas-token-altijd-base64-encoded-versturen), starting with **Profit 7**, an error message will be displayed if the AFAS-token is not sent correctly.
**Please note**: an earlier version of this document stated "End of December, 2025". That has now been changed to "Profit 7".
As already announced in the [release notes of Profit 6](news-profit6/#always-send-afas-token-in-base64-encoded-format), an error message will be given from **Profit 7** onwards if the AFAS token is not sent correctly in the Authorization header of a request.
PLEASE NOTE: an earlier version of this message stated "end of December 2025". This has now been changed to "Profit 7".

#### Wrong

`-H "Authorization: <token><version>1</version><data>37269582C95943C4AE5DCAEEEF9F4F19170BCB774D45458588517600E1C4302C</data></token>"`

``` curl
-H "Authorization: <token><version>1</version><data>37269582C95943C4AE5DCAEEEF9F4F19170BCB774D45458588517600E1C4302C</data></token>"
```

#### Correct

Send the header as `"AfasToken <base64-encoded token>"`:
`-H "Authorization: AfasToken PHRva2VuPjx2ZXJzaW9uPjE8L3ZlcnNpb24+PGRhdGE+MzcyNjk1ODJDOTU5NDNDNEFFNURDQUVFRUY5RjRGMTkxNzBCQ0I3NzRENDU0NTg1ODg1MTc2MDBFMUM0MzAyQzwvZGF0YT48L3Rva2VuPg=="`
Pass the header as `"AfasToken <base64-encoded token>"`:
```curl
-H "Authorization: AfasToken PHRva2VuPjx2ZXJzaW9uPjE8L3ZlcnNpb24+PGRhdGE+MzcyNjk1ODJDOTU5NDNDNEFFNURDQUVFRUY5RjRGMTkxNzBCQ0I3NzRENDU0NTg1ODg1MTc2MDBFMUM0MzAyQzwvZGF0YT48L3Rva2VuPg=="
```

#### SOAP

For now, it remains possible to pass the token in the Body in a SOAP message. This method is strongly discouraged and will be phased out in the future. We advise to always pass the token in the Authorization header.


## Important changes

Expand Down
17 changes: 12 additions & 5 deletions markdownpages/profit/nl/news-profit7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
author: EZW
date: 2025-11-10
date: 2025-11-25
tags: Profit7, GetConnector, UpdateConnector, Integration, Configuration
title: Nieuw in Profit 7
---
Expand All @@ -13,18 +13,25 @@ Vanaf Profit 7 is er een aantal wijzigingen in de AFAS Profit API doorgevoerd. H

### AFAS-token altijd base64-encoded versturen

Zoals in de [releasenotes van Profit 6](news-profit6/#afas-token-altijd-base64-encoded-versturen) al aangekondigd werd, zal vanaf **Profit 7** een foutmelding worden gegeven als de AFAS-token niet goed wordt doorgestuurd.
Zoals in de [releasenotes van Profit 6](news-profit6/#afas-token-altijd-base64-encoded-versturen) al aangekondigd werd, zal vanaf **Profit 7** een foutmelding worden gegeven als de AFAS-token niet goed wordt doorgestuurd in de Authorization header van een request.
LET OP: in een eerdere versie van dit bericht stond nog "eind december 2025". Dat is nu gewijzigd naar "Profit 7".

#### Fout

`-H "Authorization: <token><version>1</version><data>37269582C95943C4AE5DCAEEEF9F4F19170BCB774D45458588517600E1C4302C</data></token>"`

``` curl
-H "Authorization: <token><version>1</version><data>37269582C95943C4AE5DCAEEEF9F4F19170BCB774D45458588517600E1C4302C</data></token>"
```

#### Goed

Geef de header mee als `"AfasToken <base64-encoded token>"`:
`-H "Authorization: AfasToken PHRva2VuPjx2ZXJzaW9uPjE8L3ZlcnNpb24+PGRhdGE+MzcyNjk1ODJDOTU5NDNDNEFFNURDQUVFRUY5RjRGMTkxNzBCQ0I3NzRENDU0NTg1ODg1MTc2MDBFMUM0MzAyQzwvZGF0YT48L3Rva2VuPg=="`
```curl
-H "Authorization: AfasToken PHRva2VuPjx2ZXJzaW9uPjE8L3ZlcnNpb24+PGRhdGE+MzcyNjk1ODJDOTU5NDNDNEFFNURDQUVFRUY5RjRGMTkxNzBCQ0I3NzRENDU0NTg1ODg1MTc2MDBFMUM0MzAyQzwvZGF0YT48L3Rva2VuPg=="
```

#### SOAP

Vooralsnog blijft het in een SOAP bericht ook mogelijk om de token mee te geven in de Body. Deze methode wordt sterk ontraden en zal op termijn worden afgeschaft. We adviseren om de token altijd in de Authorization header mee te geven.

## Belangrijke wijzigingen

Expand Down