detail: 'Authentication credentials were not provided.

[buzzlightyear2k]

Im trying to call REST API from python code and encounter this error.Can someone help me ?

My code :

[candlerb]

1. Please don't post graphical screenshots. They are very hard to read, and impossible to use (e.g. to reproduce the issue, to highlight errors etc). Just copy-paste plain text: put three backticks (```) on a line of their own before and after, to format them properly as a code block in markdown.
2. Unless you've disabled authentication, you'll need to provide an Authorization: Token XXXX header, see examples here.
3. Netbox v3.2 has no /api/dcim/load-balancer/ endpoint, and AFAICS the 3.3 beta doesn't either, so presumably you are using some plugin, or a private fork of Netbox. Try accessing the core Netbox API first, e.g. /api/dcim/devices/. If your problem is only with the plugin endpoint or fork, then discuss this with the project's maintainer.

[fesenkokd]

Find this
Aug 18 09:53:48 srv-netbox-test01 gunicorn[2126]: Forbidden: /api/ipam/vlans/
Aug 18 09:54:42 srv-netbox-test01 gunicorn[2124]: Forbidden: /api/ipam/vlans/
Aug 18 09:58:20 srv-netbox-test01 gunicorn[2124]: Forbidden: /api/ipam/vlans/
Aug 18 11:50:49 srv-netbox-test01 gunicorn[2124]: Forbidden: /api/ipam/vlans/

[candlerb]

That will be because you're either not providing the Authorization header, or your proxy is not passing it through. There's nothing Netbox can do about that.

Are you sure the problem is not with Postman? I have a vague recollection of coming across a problem where Postman was dropping Authorization headers, but I can't remember the details and I can't find it by Googling. All I found was:
https://community.postman.com/t/request-headers-are-not-getting-sent/17440

If you can make it work with curl, then it's almost certainly a Postman problem. Try this:

curl -k -H "Authorization: Token XXXXXXXX" https://172.17.232.65/api/ipam/vlans/ 

[fesenkokd]

@candlerb you absolutly right, my fault in Postman config for Auth. I choose wrong Auth for workplace, now it's works properly. Thank you!

[munazza-shahzad]

Which auth did you choose, or change in postman? I am encountering the same issue.

[rgshenoy]

My problem was that I was using Bearer token in Postman and it would add Auth header as "Authorization: Bearer Token xxxxxxx" whereas it should have been just "Authorization: Token xxxxxxx". I manually added Authorization header instead of using Authorization tab in postman and it worked fine.