From 5aff9d6a8842a680c60bbc089e73daba0871569a Mon Sep 17 00:00:00 2001 From: Eric Zwaal Date: Wed, 26 Aug 2026 14:45:46 +0200 Subject: [PATCH 1/9] Add OAuth curl examples with response samples - Add curl examples for Client Credentials flow - Add curl examples for Authorization Code flow with PKCE - Include JSON response examples for token endpoints and API calls - Update token_type field values to Bearer instead of placeholder Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- markdownpages/profit/nl/authentication.md | 121 +++++++++++++++++++--- 1 file changed, 108 insertions(+), 13 deletions(-) diff --git a/markdownpages/profit/nl/authentication.md b/markdownpages/profit/nl/authentication.md index 849d7b3..ee13eba 100644 --- a/markdownpages/profit/nl/authentication.md +++ b/markdownpages/profit/nl/authentication.md @@ -81,8 +81,8 @@ Om toegang te krijgen tot de API, volg je de volgende stappen: 1. Access token ophalen 1. Roep het [token endpoint](#token-endpoint) (POST) aan met de volgende informatie in de body: 1. grant_type: client_credentials - 2. client_id: `` - 3. client_secret: `` + 2. client_id: `` + 3. client_secret: `` 2. In de response van deze aanroep vind je de volgende velden: 1. access_token: de access token die je in de Authorization header moet toevoegen. 2. refresh_token: is bij de client credentials flow altijd "null". @@ -91,6 +91,49 @@ Om toegang te krijgen tot de API, volg je de volgende stappen: 3. Access token gebruiken 1. Kopieer de access token, zet er 'Bearer' voor, en voeg hem toe in je Authorization header. +#### cURL voorbeelden + +**Token ophalen:** +```bash +curl -X POST https://.rest.afas.online/ProfitRestServices/oauth/token \ + -H "Content-Type: application/x-www-form-urlencoded" \ + -d "grant_type=client_credentials" \ + -d "client_id=" \ + -d "client_secret=" +``` + +**Response voorbeeld:** +```json +{ + "access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...", + "token_type": "Bearer", + "expires_in": 3600, + "refresh_token": null +} +``` + +**API aanroep met token:** +```bash +curl -X GET https://.rest.afas.online/ProfitRestServices/REST/V1/Employees \ + -H "Authorization: Bearer " +``` + +**Response voorbeeld:** +```json +{ + "skip": 0, + "take": 10, + "count": 150, + "rows": [ + { + "ID": 1, + "Firstname": "Jan", + "Lastname": "Jansen", + "Email": "jan.jansen@example.com" + } + ] +} +``` ### Authorization code flow with PKCE @@ -103,21 +146,21 @@ Om toegang te krijgen tot de API via de Authorization Code Flow, volg je de volg 1. Verkrijg een Autorisatiecode 1. Leid de gebruiker naar het [autorisatie endpoint](#authorization-endpoint) (GET) met de volgende parameters: 1. response_type: code - 2. client_id: `` - 3. redirect_uri: `` - 4. scope: `` - 5. state: `` - 6. code_challenge: `` - 7. code_challenge_method: `` + 2. client_id: `` + 3. redirect_uri: `` + 4. scope: `` + 5. state: `` + 6. code_challenge: `` + 7. code_challenge_method: `S256` 2. De gebruiker logt in en geeft toestemming. Na toestemming wordt de gebruiker teruggeleid naar de opgegeven redirect_uri met een autorisatiecode. 2. Wissel de Autorisatiecode in voor een Access Token 1. Roep het [token endpoint](#token-endpoint) (POST) aan met de volgende informatie in de body: 1. grant_type: authorization_code - 2. code: `` - 3. redirect_uri: `` - 4. client_id: `` - 5. client_secret: `` - 6. code_verifier: `` + 2. code: `` + 3. redirect_uri: `` + 4. client_id: `` + 5. client_secret: `` + 6. code_verifier: `` 3. In de response van deze aanroep vind je de volgende velden: 1. access_token: de access token die je in de Authorization header moet toevoegen. 2. refresh_token: een token dat kan worden gebruikt om een nieuw access token te verkrijgen. @@ -126,6 +169,58 @@ Om toegang te krijgen tot de API via de Authorization Code Flow, volg je de volg 3. Access Token Gebruiken 1. Kopieer de access token, zet er 'Bearer' voor, en voeg hem toe in je Authorization header. +#### cURL voorbeelden + +**Stap 1: Gebruiker redirecten naar autorisatie endpoint:** +```bash +curl -X GET "https://.rest.afas.online/ProfitRestServices/oauth/authorize?response_type=code&client_id=&redirect_uri=&scope=&state=&code_challenge=&code_challenge_method=S256" +``` + +**Stap 2: Token ophalen met autorisatiecode:** +```bash +curl -X POST https://.rest.afas.online/ProfitRestServices/oauth/token \ + -H "Content-Type: application/x-www-form-urlencoded" \ + -d "grant_type=authorization_code" \ + -d "code=" \ + -d "redirect_uri=" \ + -d "client_id=" \ + -d "client_secret=" \ + -d "code_verifier=" +``` + +**Response voorbeeld:** +```json +{ + "access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...", + "token_type": "Bearer", + "expires_in": 3600, + "refresh_token": "50c90d85-a7aa-4e8a-a9b8-..." +} +``` + +**Stap 3: API aanroep met token:** +```bash +curl -X GET https://.rest.afas.online/ProfitRestServices/REST/V1/Employees \ + -H "Authorization: Bearer " +``` + +**Response voorbeeld:** +```json +{ + "skip": 0, + "take": 10, + "count": 150, + "rows": [ + { + "ID": 1, + "Firstname": "Jan", + "Lastname": "Jansen", + "Email": "jan.jansen@example.com" + } + ] +} +``` + ### OAuth & SOAP API Bovenstaande beschrijving voor beide flows geldt ook wanneer je gebruikmaakt van de SOAP API. Het is belangrijk dat je het Bearer-token meegeeft in de header en niet in de body. From 53347da2fb15a29c7a9d19eaac8f19f466dfa063 Mon Sep 17 00:00:00 2001 From: Eric Zwaal Date: Wed, 26 Aug 2026 14:53:48 +0200 Subject: [PATCH 2/9] Restore parameter descriptions in Authorization Code flow - Restore 'state' description for CSRF protection - Restore 'code_challenge' and 'code_challenge_method' descriptions - Restore 'code_verifier' description Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- markdownpages/profit/nl/authentication.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/markdownpages/profit/nl/authentication.md b/markdownpages/profit/nl/authentication.md index ee13eba..0ea3298 100644 --- a/markdownpages/profit/nl/authentication.md +++ b/markdownpages/profit/nl/authentication.md @@ -149,9 +149,9 @@ Om toegang te krijgen tot de API via de Authorization Code Flow, volg je de volg 2. client_id: `` 3. redirect_uri: `` 4. scope: `` - 5. state: `` - 6. code_challenge: `` - 7. code_challenge_method: `S256` + 5. state: `` + 6. code_challenge: `` + 7. code_challenge_method: `` 2. De gebruiker logt in en geeft toestemming. Na toestemming wordt de gebruiker teruggeleid naar de opgegeven redirect_uri met een autorisatiecode. 2. Wissel de Autorisatiecode in voor een Access Token 1. Roep het [token endpoint](#token-endpoint) (POST) aan met de volgende informatie in de body: @@ -160,7 +160,7 @@ Om toegang te krijgen tot de API via de Authorization Code Flow, volg je de volg 3. redirect_uri: `` 4. client_id: `` 5. client_secret: `` - 6. code_verifier: `` + 6. code_verifier: `` 3. In de response van deze aanroep vind je de volgende velden: 1. access_token: de access token die je in de Authorization header moet toevoegen. 2. refresh_token: een token dat kan worden gebruikt om een nieuw access token te verkrijgen. From 07bb9e3d40f1598d904158cdcc1d21bcdd1b8e0a Mon Sep 17 00:00:00 2001 From: Eric Zwaal Date: Wed, 26 Aug 2026 14:56:19 +0200 Subject: [PATCH 3/9] Add OAuth curl examples with response samples (English) - Add curl examples for Client Credentials flow - Add curl examples for Authorization Code flow with PKCE - Include JSON response examples for token endpoints and API calls - Update token_type field values to Bearer instead of placeholder - Restore parameter descriptions (state, code_challenge, code_challenge_method, code_verifier) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- markdownpages/profit/en/authentication.md | 113 ++++++++++++++++++++-- 1 file changed, 104 insertions(+), 9 deletions(-) diff --git a/markdownpages/profit/en/authentication.md b/markdownpages/profit/en/authentication.md index a279a98..3c2795f 100644 --- a/markdownpages/profit/en/authentication.md +++ b/markdownpages/profit/en/authentication.md @@ -82,8 +82,8 @@ To access the API, follow these steps: 1. Obtain an access token 1. Call the [token endpoint](#token-endpoint) (POST) with the following information in the body: 1. grant_type: client_credentials - 2. client_id: `` - 3. client_secret: `` + 2. client_id: `` + 3. client_secret: `` 2. In the response of this call you will find the following fields: 1. access_token: the access token you must add to the Authorization header. 2. refresh_token: for the client credentials flow this is always "null". @@ -92,6 +92,49 @@ To access the API, follow these steps: 3. Use the access token 1. Copy the access token, prefix it with 'Bearer', and add it to your Authorization header. +#### cURL examples + +**Retrieve token:** +\`\`\`bash +curl -X POST https://.rest.afas.online/ProfitRestServices/oauth/token \ + -H "Content-Type: application/x-www-form-urlencoded" \ + -d "grant_type=client_credentials" \ + -d "client_id=" \ + -d "client_secret=" +\`\`\` + +**Response example:** +\`\`\`json +{ + "access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...", + "token_type": "Bearer", + "expires_in": 3600, + "refresh_token": null +} +\`\`\` + +**API call with token:** +\`\`\`bash +curl -X GET https://.rest.afas.online/ProfitRestServices/REST/V1/Employees \ + -H "Authorization: Bearer " +\`\`\` + +**Response example:** +\`\`\`json +{ + "skip": 0, + "take": 10, + "count": 150, + "rows": [ + { + "ID": 1, + "Firstname": "John", + "Lastname": "Doe", + "Email": "john.doe@example.com" + } + ] +} +\`\`\` ### Authorization code flow with PKCE @@ -104,9 +147,9 @@ To access the API via the Authorization Code Flow, follow these steps: 1. Obtain an authorization code 1. Redirect the user to the [authorization endpoint](#authorization-endpoint) (GET) with the following parameters: 1. response_type: code - 2. client_id: `` - 3. redirect_uri: `` - 4. scope: `` + 2. client_id: `` + 3. redirect_uri: `` + 4. scope: `` 5. state: `` 6. code_challenge: `` 7. code_challenge_method: `` @@ -114,10 +157,10 @@ To access the API via the Authorization Code Flow, follow these steps: 2. Exchange the authorization code for an access token 1. Call the [token endpoint](#token-endpoint) (POST) with the following information in the body: 1. grant_type: authorization_code - 2. code: `` - 3. redirect_uri: `` - 4. client_id: `` - 5. client_secret: `` + 2. code: `` + 3. redirect_uri: `` + 4. client_id: `` + 5. client_secret: `` 6. code_verifier: `` 3. In the response of this call you will find the following fields: 1. access_token: the access token you must add to the Authorization header. @@ -127,6 +170,58 @@ To access the API via the Authorization Code Flow, follow these steps: 3. Use the access token 1. Copy the access token, prefix it with 'Bearer', and add it to your Authorization header. +#### cURL examples + +**Step 1: Redirect user to authorization endpoint:** +\`\`\`bash +curl -X GET "https://.rest.afas.online/ProfitRestServices/oauth/authorize?response_type=code&client_id=&redirect_uri=&scope=&state=&code_challenge=&code_challenge_method=S256" +\`\`\` + +**Step 2: Retrieve token with authorization code:** +\`\`\`bash +curl -X POST https://.rest.afas.online/ProfitRestServices/oauth/token \ + -H "Content-Type: application/x-www-form-urlencoded" \ + -d "grant_type=authorization_code" \ + -d "code=" \ + -d "redirect_uri=" \ + -d "client_id=" \ + -d "client_secret=" \ + -d "code_verifier=" +\`\`\` + +**Response example:** +\`\`\`json +{ + "access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...", + "token_type": "Bearer", + "expires_in": 3600, + "refresh_token": "50c90d85-a7aa-4e8a-a9b8-..." +} +\`\`\` + +**Step 3: API call with token:** +\`\`\`bash +curl -X GET https://.rest.afas.online/ProfitRestServices/REST/V1/Employees \ + -H "Authorization: Bearer " +\`\`\` + +**Response example:** +\`\`\`json +{ + "skip": 0, + "take": 10, + "count": 150, + "rows": [ + { + "ID": 1, + "Firstname": "John", + "Lastname": "Doe", + "Email": "john.doe@example.com" + } + ] +} +\`\`\` + ### OAuth & SOAP API The description above for both flows also applies when using the SOAP API. It is important to include the Bearer token in the header and not in the body. From 705dba73ea5c6334c3ebac793d0cf3bc76e723e9 Mon Sep 17 00:00:00 2001 From: Eric Zwaal Date: Wed, 26 Aug 2026 14:58:43 +0200 Subject: [PATCH 4/9] Update curl examples with realistic API endpoints and response formats - Change API endpoint from REST/V1/Employees to connectors/Profit_Address - Update response structure to match actual API format (skip, take, rows) - Use actual address data from get-connector examples - Add Accept header to API calls - Remove 'count' field from response (not in actual API response) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- markdownpages/profit/en/authentication.md | 44 ++++++++++++++--------- markdownpages/profit/nl/authentication.md | 44 ++++++++++++++--------- 2 files changed, 56 insertions(+), 32 deletions(-) diff --git a/markdownpages/profit/en/authentication.md b/markdownpages/profit/en/authentication.md index 3c2795f..1df15bc 100644 --- a/markdownpages/profit/en/authentication.md +++ b/markdownpages/profit/en/authentication.md @@ -115,22 +115,28 @@ curl -X POST https://.rest.afas.online/ProfitRestServices/oau **API call with token:** \`\`\`bash -curl -X GET https://.rest.afas.online/ProfitRestServices/REST/V1/Employees \ - -H "Authorization: Bearer " +curl -X GET "https://.rest.afas.online/ProfitRestServices/connectors/Profit_Address?skip=0&take=100" \ + -H "Authorization: Bearer " \ + -H "Accept: application/json" \`\`\` **Response example:** \`\`\`json { "skip": 0, - "take": 10, - "count": 150, + "take": 2, "rows": [ { - "ID": 1, - "Firstname": "John", - "Lastname": "Doe", - "Email": "john.doe@example.com" + "AddressId": 1, + "AddressLine": "Stadsring 69, 3811 HN AMERSFOORT", + "PoBox": false, + "Address": "Stadsring", + "Number": 69, + "ZipCode": "3811 HN", + "Recidence": "Amersfoort", + "Country": "NL", + "CreateDate": "2012-11-22T09:49:49Z", + "ModifiedDate": "2015-01-26T16:57:43Z" } ] } @@ -201,22 +207,28 @@ curl -X POST https://.rest.afas.online/ProfitRestServices/oau **Step 3: API call with token:** \`\`\`bash -curl -X GET https://.rest.afas.online/ProfitRestServices/REST/V1/Employees \ - -H "Authorization: Bearer " +curl -X GET "https://.rest.afas.online/ProfitRestServices/connectors/Profit_Address?skip=0&take=100" \ + -H "Authorization: Bearer " \ + -H "Accept: application/json" \`\`\` **Response example:** \`\`\`json { "skip": 0, - "take": 10, - "count": 150, + "take": 2, "rows": [ { - "ID": 1, - "Firstname": "John", - "Lastname": "Doe", - "Email": "john.doe@example.com" + "AddressId": 1, + "AddressLine": "Stadsring 69, 3811 HN AMERSFOORT", + "PoBox": false, + "Address": "Stadsring", + "Number": 69, + "ZipCode": "3811 HN", + "Recidence": "Amersfoort", + "Country": "NL", + "CreateDate": "2012-11-22T09:49:49Z", + "ModifiedDate": "2015-01-26T16:57:43Z" } ] } diff --git a/markdownpages/profit/nl/authentication.md b/markdownpages/profit/nl/authentication.md index 0ea3298..aa7fb42 100644 --- a/markdownpages/profit/nl/authentication.md +++ b/markdownpages/profit/nl/authentication.md @@ -114,22 +114,28 @@ curl -X POST https://.rest.afas.online/ProfitRestServices/oauth **API aanroep met token:** ```bash -curl -X GET https://.rest.afas.online/ProfitRestServices/REST/V1/Employees \ - -H "Authorization: Bearer " +curl -X GET "https://.rest.afas.online/ProfitRestServices/connectors/Profit_Address?skip=0&take=100" \ + -H "Authorization: Bearer " \ + -H "Accept: application/json" ``` **Response voorbeeld:** ```json { "skip": 0, - "take": 10, - "count": 150, + "take": 2, "rows": [ { - "ID": 1, - "Firstname": "Jan", - "Lastname": "Jansen", - "Email": "jan.jansen@example.com" + "AddressId": 1, + "AddressLine": "Stadsring 69, 3811 HN AMERSFOORT", + "PoBox": false, + "Address": "Stadsring", + "Number": 69, + "ZipCode": "3811 HN", + "Recidence": "Amersfoort", + "Country": "NL", + "CreateDate": "2012-11-22T09:49:49Z", + "ModifiedDate": "2015-01-26T16:57:43Z" } ] } @@ -200,22 +206,28 @@ curl -X POST https://.rest.afas.online/ProfitRestServices/oauth **Stap 3: API aanroep met token:** ```bash -curl -X GET https://.rest.afas.online/ProfitRestServices/REST/V1/Employees \ - -H "Authorization: Bearer " +curl -X GET "https://.rest.afas.online/ProfitRestServices/connectors/Profit_Address?skip=0&take=100" \ + -H "Authorization: Bearer " \ + -H "Accept: application/json" ``` **Response voorbeeld:** ```json { "skip": 0, - "take": 10, - "count": 150, + "take": 2, "rows": [ { - "ID": 1, - "Firstname": "Jan", - "Lastname": "Jansen", - "Email": "jan.jansen@example.com" + "AddressId": 1, + "AddressLine": "Stadsring 69, 3811 HN AMERSFOORT", + "PoBox": false, + "Address": "Stadsring", + "Number": 69, + "ZipCode": "3811 HN", + "Recidence": "Amersfoort", + "Country": "NL", + "CreateDate": "2012-11-22T09:49:49Z", + "ModifiedDate": "2015-01-26T16:57:43Z" } ] } From 9e076e997d1d93acf255c1048d8cf3f5e7a3325e Mon Sep 17 00:00:00 2001 From: Eric Zwaal Date: Wed, 26 Aug 2026 15:10:56 +0200 Subject: [PATCH 5/9] PROJECT#RSY00007 Verbetering OAuth documentatie --- markdownpages/profit/en/authentication.md | 72 +++++++++++------------ markdownpages/profit/nl/authentication.md | 36 ++++++------ 2 files changed, 54 insertions(+), 54 deletions(-) diff --git a/markdownpages/profit/en/authentication.md b/markdownpages/profit/en/authentication.md index 1df15bc..64964e0 100644 --- a/markdownpages/profit/en/authentication.md +++ b/markdownpages/profit/en/authentication.md @@ -95,36 +95,36 @@ To access the API, follow these steps: #### cURL examples **Retrieve token:** -\`\`\`bash +```bash curl -X POST https://.rest.afas.online/ProfitRestServices/oauth/token \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "grant_type=client_credentials" \ -d "client_id=" \ -d "client_secret=" -\`\`\` +``` **Response example:** -\`\`\`json +```json { "access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...", "token_type": "Bearer", "expires_in": 3600, "refresh_token": null } -\`\`\` +``` **API call with token:** -\`\`\`bash +```bash curl -X GET "https://.rest.afas.online/ProfitRestServices/connectors/Profit_Address?skip=0&take=100" \ - -H "Authorization: Bearer " \ - -H "Accept: application/json" -\`\`\` + -H "Accept: application/json" \ + -H "Authorization: Bearer " +``` **Response example:** -\`\`\`json +```json { "skip": 0, - "take": 2, + "take": 100, "rows": [ { "AddressId": 1, @@ -134,13 +134,11 @@ curl -X GET "https://.rest.afas.online/ProfitRestServices/con "Number": 69, "ZipCode": "3811 HN", "Recidence": "Amersfoort", - "Country": "NL", - "CreateDate": "2012-11-22T09:49:49Z", - "ModifiedDate": "2015-01-26T16:57:43Z" + "Country": "NL" } ] } -\`\`\` +``` ### Authorization code flow with PKCE @@ -179,12 +177,12 @@ To access the API via the Authorization Code Flow, follow these steps: #### cURL examples **Step 1: Redirect user to authorization endpoint:** -\`\`\`bash +```bash curl -X GET "https://.rest.afas.online/ProfitRestServices/oauth/authorize?response_type=code&client_id=&redirect_uri=&scope=&state=&code_challenge=&code_challenge_method=S256" -\`\`\` +``` **Step 2: Retrieve token with authorization code:** -\`\`\`bash +```bash curl -X POST https://.rest.afas.online/ProfitRestServices/oauth/token \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "grant_type=authorization_code" \ @@ -193,30 +191,30 @@ curl -X POST https://.rest.afas.online/ProfitRestServices/oau -d "client_id=" \ -d "client_secret=" \ -d "code_verifier=" -\`\`\` +``` **Response example:** -\`\`\`json +```json { "access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...", "token_type": "Bearer", "expires_in": 3600, "refresh_token": "50c90d85-a7aa-4e8a-a9b8-..." } -\`\`\` +``` **Step 3: API call with token:** -\`\`\`bash +```bash curl -X GET "https://.rest.afas.online/ProfitRestServices/connectors/Profit_Address?skip=0&take=100" \ - -H "Authorization: Bearer " \ - -H "Accept: application/json" -\`\`\` + -H "Accept: application/json" \ + -H "Authorization: Bearer " +``` **Response example:** -\`\`\`json +```json { "skip": 0, - "take": 2, + "take": 100, "rows": [ { "AddressId": 1, @@ -226,30 +224,32 @@ curl -X GET "https://.rest.afas.online/ProfitRestServices/con "Number": 69, "ZipCode": "3811 HN", "Recidence": "Amersfoort", - "Country": "NL", - "CreateDate": "2012-11-22T09:49:49Z", - "ModifiedDate": "2015-01-26T16:57:43Z" + "Country": "NL" } ] } -\`\`\` +``` ### OAuth & SOAP API The description above for both flows also applies when using the SOAP API. It is important to include the Bearer token in the header and not in the body. ### Token endpoint -Production: https://``.rest.afas.online/ProfitRestServices/oauth/token +These endpoints apply to both REST and SOAP. -Accept: : https://``.restaccept.afas.online/ProfitRestServices/oauth/token +**Production**: https://``.rest.afas.online/ProfitRestServices/oauth/token -Test: https://``.resttest.afas.online/ProfitRestServices/oauth/token +**Accept**: https://``.restaccept.afas.online/ProfitRestServices/oauth/token + +**Test**: https://``.resttest.afas.online/ProfitRestServices/oauth/token ### Authorization endpoint -Production: https://``.rest.afas.online/ProfitRestServices/oauth/authorize +These endpoints apply to both REST and SOAP. + +**Production**: https://``.rest.afas.online/ProfitRestServices/oauth/authorize -Accept: https://``.restaccept.afas.online/ProfitRestServices/oauth/authorize +**Accept**: https://``.restaccept.afas.online/ProfitRestServices/oauth/authorize -Test: https://``.resttest.afas.online/ProfitRestServices/oauth/authorize +**Test**: https://``.resttest.afas.online/ProfitRestServices/oauth/authorize ### Read more diff --git a/markdownpages/profit/nl/authentication.md b/markdownpages/profit/nl/authentication.md index aa7fb42..cf0b07d 100644 --- a/markdownpages/profit/nl/authentication.md +++ b/markdownpages/profit/nl/authentication.md @@ -115,15 +115,15 @@ curl -X POST https://.rest.afas.online/ProfitRestServices/oauth **API aanroep met token:** ```bash curl -X GET "https://.rest.afas.online/ProfitRestServices/connectors/Profit_Address?skip=0&take=100" \ - -H "Authorization: Bearer " \ - -H "Accept: application/json" + -H "Accept: application/json" \ + -H "Authorization: Bearer " ``` **Response voorbeeld:** ```json { "skip": 0, - "take": 2, + "take": 100, "rows": [ { "AddressId": 1, @@ -133,9 +133,7 @@ curl -X GET "https://.rest.afas.online/ProfitRestServices/conne "Number": 69, "ZipCode": "3811 HN", "Recidence": "Amersfoort", - "Country": "NL", - "CreateDate": "2012-11-22T09:49:49Z", - "ModifiedDate": "2015-01-26T16:57:43Z" + "Country": "NL" } ] } @@ -207,15 +205,15 @@ curl -X POST https://.rest.afas.online/ProfitRestServices/oauth **Stap 3: API aanroep met token:** ```bash curl -X GET "https://.rest.afas.online/ProfitRestServices/connectors/Profit_Address?skip=0&take=100" \ - -H "Authorization: Bearer " \ - -H "Accept: application/json" + -H "Accept: application/json" \ + -H "Authorization: Bearer " ``` **Response voorbeeld:** ```json { "skip": 0, - "take": 2, + "take": 100, "rows": [ { "AddressId": 1, @@ -225,9 +223,7 @@ curl -X GET "https://.rest.afas.online/ProfitRestServices/conne "Number": 69, "ZipCode": "3811 HN", "Recidence": "Amersfoort", - "Country": "NL", - "CreateDate": "2012-11-22T09:49:49Z", - "ModifiedDate": "2015-01-26T16:57:43Z" + "Country": "NL" } ] } @@ -238,18 +234,22 @@ Bovenstaande beschrijving voor beide flows geldt ook wanneer je gebruikmaakt van ### Token endpoint -Productie: https://``.rest.afas.online/ProfitRestServices/oauth/token +Deze endpoints gelden zowel voor REST als voor SOAP. -Accept: : https://``.restaccept.afas.online/ProfitRestServices/oauth/token +**Productie**: https://``.rest.afas.online/ProfitRestServices/oauth/token -Test: https://``.resttest.afas.online/ProfitRestServices/oauth/token +**Accept**: : https://``.restaccept.afas.online/ProfitRestServices/oauth/token + +**Test**: https://``.resttest.afas.online/ProfitRestServices/oauth/token ### Authorization endpoint -Productie: https://``.rest.afas.online/ProfitRestServices/oauth/authorize +Deze endpoints gelden zowel voor REST als voor SOAP. + +**Productie**: https://``.rest.afas.online/ProfitRestServices/oauth/authorize -Accept: https://``.restaccept.afas.online/ProfitRestServices/oauth/authorize +**Accept**: https://``.restaccept.afas.online/ProfitRestServices/oauth/authorize -Test: https://``.resttest.afas.online/ProfitRestServices/oauth/authorize +**Test**: https://``.resttest.afas.online/ProfitRestServices/oauth/authorize From 02e498e2cca1f15326ab493661895e62d4e523eb Mon Sep 17 00:00:00 2001 From: Eric Zwaal Date: Wed, 26 Aug 2026 15:13:31 +0200 Subject: [PATCH 6/9] Fix typo in Accept endpoint description (Dutch) Remove duplicate colon in Accept endpoint line. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- markdownpages/profit/nl/authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/markdownpages/profit/nl/authentication.md b/markdownpages/profit/nl/authentication.md index cf0b07d..c3435cd 100644 --- a/markdownpages/profit/nl/authentication.md +++ b/markdownpages/profit/nl/authentication.md @@ -238,7 +238,7 @@ Deze endpoints gelden zowel voor REST als voor SOAP. **Productie**: https://``.rest.afas.online/ProfitRestServices/oauth/token -**Accept**: : https://``.restaccept.afas.online/ProfitRestServices/oauth/token +**Accept**: https://``.restaccept.afas.online/ProfitRestServices/oauth/token **Test**: https://``.resttest.afas.online/ProfitRestServices/oauth/token From 490581a8ea4d55e64c6f321ce9614e00b4253ebf Mon Sep 17 00:00:00 2001 From: Eric Zwaal Date: Wed, 26 Aug 2026 15:14:41 +0200 Subject: [PATCH 7/9] Update frontmatter date to 2026-08-26 - Update date in Dutch authentication.md - Update date in English authentication.md Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- markdownpages/profit/en/authentication.md | 2 +- markdownpages/profit/nl/authentication.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/markdownpages/profit/en/authentication.md b/markdownpages/profit/en/authentication.md index 64964e0..57ad15d 100644 --- a/markdownpages/profit/en/authentication.md +++ b/markdownpages/profit/en/authentication.md @@ -1,6 +1,6 @@ --- author: CLN -date: 2026-07-31 +date: 2026-08-26 tags: GetConnector, AppConnector, Integration, Configuration, Authentication, Authorization title: Authentication --- diff --git a/markdownpages/profit/nl/authentication.md b/markdownpages/profit/nl/authentication.md index c3435cd..3e30ccb 100644 --- a/markdownpages/profit/nl/authentication.md +++ b/markdownpages/profit/nl/authentication.md @@ -1,6 +1,6 @@ --- author: CLN -date: 2026-07-31 +date: 2026-08-26 tags: GetConnector, AppConnector, Integration, Configuration, Authentication, Authorization title: Authenticatie --- From e302c213088d74feff3bd744199ee6378926c63c Mon Sep 17 00:00:00 2001 From: Eric Zwaal <113451662+ezw2000@users.noreply.github.com> Date: Wed, 26 Aug 2026 15:33:41 +0200 Subject: [PATCH 8/9] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- markdownpages/profit/nl/authentication.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/markdownpages/profit/nl/authentication.md b/markdownpages/profit/nl/authentication.md index 3e30ccb..e6f1498 100644 --- a/markdownpages/profit/nl/authentication.md +++ b/markdownpages/profit/nl/authentication.md @@ -177,7 +177,8 @@ Om toegang te krijgen tot de API via de Authorization Code Flow, volg je de volg **Stap 1: Gebruiker redirecten naar autorisatie endpoint:** ```bash -curl -X GET "https://.rest.afas.online/ProfitRestServices/oauth/authorize?response_type=code&client_id=&redirect_uri=&scope=&state=&code_challenge=&code_challenge_method=S256" +# Open deze URL in een browser: +https://.rest.afas.online/ProfitRestServices/oauth/authorize?response_type=code&client_id=&redirect_uri=&scope=&state=&code_challenge=&code_challenge_method=S256 ``` **Stap 2: Token ophalen met autorisatiecode:** From b3556fbb5f6791040966ee3b2f009a677bca8466 Mon Sep 17 00:00:00 2001 From: Eric Zwaal <113451662+ezw2000@users.noreply.github.com> Date: Wed, 26 Aug 2026 15:33:53 +0200 Subject: [PATCH 9/9] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- markdownpages/profit/en/authentication.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/markdownpages/profit/en/authentication.md b/markdownpages/profit/en/authentication.md index 57ad15d..4fc56f3 100644 --- a/markdownpages/profit/en/authentication.md +++ b/markdownpages/profit/en/authentication.md @@ -178,7 +178,8 @@ To access the API via the Authorization Code Flow, follow these steps: **Step 1: Redirect user to authorization endpoint:** ```bash -curl -X GET "https://.rest.afas.online/ProfitRestServices/oauth/authorize?response_type=code&client_id=&redirect_uri=&scope=&state=&code_challenge=&code_challenge_method=S256" +# Open this URL in a browser: +https://.rest.afas.online/ProfitRestServices/oauth/authorize?response_type=code&client_id=&redirect_uri=&scope=&state=&code_challenge=&code_challenge_method=S256 ``` **Step 2: Retrieve token with authorization code:**