XAPI 403 denied error

[Remco Straaten]

We are currently testing APIs within 3CX. We are able to perform authentication, but when we make an API call afterwards, we receive a 403 “access denied” response.

Various topics mention console restrictions; we have configured these and even disabled them, but it made no difference. We have also selected the default department with the corresponding system owner role.

Does anyone have any tips or suggestions on how to resolve this?

 

[N_G]

Are you doing this with an AI/ENT edition? This is required for the API

 

[Remco Straaten]

Yes we are doing this.

 

[Evolute IT]

Console restrictions?

 

[Remco Straaten]

Disabled.

 

[Evolute IT]

Disabled.

Which API login method are you using? And what version and license edition of the PBX do you have?

 

[Remco Straaten]

Hi,

We tried different method. For example the 3CX powershell GIT page.
https://github.com/luxzg/3CX-XAPI_examples

We are using the Enterprise license with version Version 20.0 Update 8 (Build 1131 Release)

 

[Evolute IT]

Hi,

We tried different method. For example the 3CX powershell GIT page.
https://github.com/luxzg/3CX-XAPI_examples

We are using the Enterprise license with version Version 20.0 Update 8 (Build 1131 Release)

Those are third-party projects. No one here will support these.

If you need certainty, use cURL and your own code. The XAPI can change at anytime and libraries like this are not reliable long-term.

 

[Remco Straaten]

Understand. But we tried multiple ways, also the simple curl and our own api code.

 

[Evolute IT]

Understand. But we tried multiple ways, also the simple curl and our own api code.

There must be something wrong or misconfigured, because we use the XAPI daily and never get this error. It's usually console restrictions or bad config.

Also, try both a system owner and client credentials on the different endpoints to make sure.

 

[Remco Straaten]

We have created an seperate user for the API with System Owner rights and now it is working.