getting postman error when calling a webservice - The server has rejected the client credentials

(1) Share

Report

Posted on by WF-14012240-0

In Postman - I have clientid, tenantid, secret values
I have retrieved an oauth token succesfully

but subsequent calls retyurn an arror example
https://api.businesscentral.dynamics.com/v2.0/{{oAuthTenantID}}/Sandbox/ODataV4/Company('CRONUS%20USA%2C%20Inc.')/companies

{"error":{"code":"Authentication_InvalidCredentials","message":"The server has rejected the client credentials. CorrelationId: fb65aa3e-99d6-459a-ae17-690b0ec1b7b7."}}

Categories:

Dynamics 365 general

I have the same question (0)

All responses (6)

Answers (1)

Suggested answer

Muhammad Shahzad Sh... 2,336 Most Valuable Professional on at

Like (1)

Report

getting postman error when calling a webservice - The server has rejected the client credentials

1. Expired Access Token
- OAuth tokens have a limited lifespan (typically 1 hour).
- Solution: Refresh the token before making subsequent calls.

2. Incorrect API URL Structure
- Ensure the URL follows the correct format:
https://api.businesscentral.dynamics.com/v2.0/{{tenantId}}/{{environmentName}}/api/...
- Common Mistake: Using `Sandbox` instead of the actual environment name.

3. Missing or Incorrect Scope in Token Request
- The token must include the correct scope (e.g., `https://api.businesscentral.dynamics.com/.default`).
- Postman Example:
{
      "grant_type": "client_credentials",
      "client_id": "{{clientId}}",
      "client_secret": "{{clientSecret}}",
      "scope": "https://api.businesscentral.dynamics.com/.default"
}

Was this reply helpful? Yes No
Suggested answer

Ramesh Kumar 7,521 Super User 2025 Season 2 on at

Like (1)

Report

getting postman error when calling a webservice - The server has rejected the client credentials

Typically indicates an issue with the configuration of your Azure Active Directory (Azure AD) application or its permissions within Business Central. Assign Super your permission and try again.

https://yzhums.com/20690/?

https://learn.microsoft.com/en-us/answers/questions/401692/the-credentials-provided-are-incorrect-bc-oauth-2?

Thanks

Ramesh

If this was helpful, please check the "Does this answer your question?" box and mark it as verified.

Was this reply helpful? Yes No
Jonas "Jones" Melgaard 4,894 Super User 2025 Season 2 on at

Like (1)

Report

getting postman error when calling a webservice - The server has rejected the client credentials

Moved to the SMC forum, since this is related to Business Central.

Do notice that blacking out text in the question text editor will not hide the text.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 93,222 Super User 2025 Season 2 on at

Like (0)

Report

getting postman error when calling a webservice - The server has rejected the client credentials

Hi, It looks like you haven't added this app in BC's Microsoft Entra Application and given permissions.

You can check it first.

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 19,357 Super User 2025 Season 2 on at

Like (1)

Report

getting postman error when calling a webservice - The server has rejected the client credentials

Adding more: you should add the extension in permission.

https://yzhums.com/20690/

Was this reply helpful? Yes No
Verified answer

Sohail Ahmed 11,095 Super User 2025 Season 2 on at

Like (2)

Report
getting postman error when calling a webservice - The server has rejected the client credentials

You might be missing necessary permissions inside Business Central for the app you're using.

Here's how to fix it:

In Business Central, search for “Microsoft Entra Applications”.

Click New.

Enter your Application (client) ID and a name.

Under User Permissions, assign the following permissions:

D365 BASIC

SUPER (DATA) or other relevant permission sets based on your needs

This grants your registered Azure AD app the right access level inside BC.

📎 Find the attached screenshot for your reference.

Click Grant Consent (You must be an admin for this)

Once done, retry your request — it should authenticate correctly.

Mark below checkbox to make this answer Verified if it helps you.

Was this reply helpful? Yes No