Netbox and Postman API

[jc-chuckles]

Its my first delve into any form of API integration and I'm struggling with getting Postman to work.

I've used the Netbox API overview to allow Postman to provision an API token, this worked fine and a v2 token has been created.

What I'm struggling with is using that token, whichever way I try and integrate the token using either API token or Bearer token in Postman I continually get 403 forbidden Invalid v1 token.

Its probably going to be something strighforward to fix but at the moment I've not managed to get this working.

Is there anyone in the community who could point me in the right direction to get this working?

Thanks

Jon

[pheus]

Hi @jc-chuckles,

Sorry you’re having trouble getting this working. API authentication can be a little confusing the first time.

The “Invalid v1 token” message suggests that NetBox is receiving the token in the legacy v1 format. A v2 token must use the complete value, including the nbt_ prefix, key, and token:

Authorization: Bearer nbt_<key>.<token>

In Postman, select Bearer Token as the authorization type and enter only nbt_<key>.<token> in the Token field. Postman will add the Bearer prefix automatically.

You can find the full format and an example in the REST API documentation:
https://netboxlabs.com/docs/netbox/integrations/rest-api/#authenticating-to-the-api

Hope this helps get you pointed in the right direction!

[markkuleinio]

token must use the complete value, including the nbt_ prefix, key, and token

Yes, the token syntax&terminology is somewhat confusing, see also #22917 .

[jc-chuckles]

Martin Changing the format to the below stopped the invalid V1 Token but now I get Invalid V2 token. I've got in my Environment variables key and token which matches the V2 key and token details, the key being the shorter of the two. I have a request of GET https://url/api/dcim/sites/ and a Bearer Token enabled with nbt_<key>.<token>. Thanks Jon From: Martin Hauser ***@***.***> Sent: 04 September 2026 14:52 To: netbox-community/netbox ***@***.***> Cc: HILL, Jon (LINCOLNSHIRE COMMUNITY AND HOSPITALS NHS GROUP - RWD) ***@***.***>; Mention ***@***.***> Subject: Re: [netbox-community/netbox] Netbox and Postman API (Discussion #23131) This message originated from outside of NHS.net Connect. Please do not click links or open attachments unless you recognise the sender and know the content is safe. Hi @jc-chuckles<https://github.com/jc-chuckles>, Sorry you're having trouble getting this working. API authentication can be a little confusing the first time. The "Invalid v1 token" message suggests that NetBox is receiving the token in the legacy v1 format. A v2 token must use the complete value, including the nbt_ prefix, key, and token: Authorization: Bearer nbt_<key>.<token> In Postman, select Bearer Token as the authorization type and enter only nbt_<key>.<token> in the Token field. Postman will add the Bearer prefix automatically. You can find the full format and an example in the REST API documentation: https://netboxlabs.com/docs/netbox/integrations/rest-api/#authenticating-to-the-api Hope this helps get you pointed in the right direction! - Reply to this email directly, view it on GitHub<#23131?email_source=notifications&email_token=BTJJ2TX35UPRMZOFGNAXN4D5NLCG3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSHEYDENRWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18290266>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BTJJ2TRABIBAJSZD2DUCAGD5NLCG3AVCNFSNUABHKJSXA33TNF2G64TZHM2TENZZGY2TSNR3IRUXGY3VONZWS33OHMYTANZUHE4TON5BOYBA>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/BTJJ2TRNU3RHVLFGST3ELCD5NLCG3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSHEYDENRWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android<https://github.com/notifications/mobile/android/BTJJ2TUTRL5PTPT5H6IFUAD5NLCG3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSHEYDENRWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> ************************************************************************************** ****************************** This message may contain confidential information. If you are not the intended recipient please: i) inform the sender that you have received the message in error before deleting it; and ii) do not disclose, copy or distribute information in this e-mail or take any action in relation to its content (to do so is strictly prohibited and may be unlawful). Thank you for your co-operation. NHS.net Connect is the secure email, collaboration and directory service available for all NHS staff in England. NHS.net Connect is approved for exchanging patient data and other sensitive information with NHS.net Connect and other accredited email services. For more information and to find out how you can switch visit Joining NHS.net Connect - NHS.net Connect Support<https://support.nhs.net/article-categories/joining-nhsmail/>