That should not be the case, I think API is open to any account now by default. Please check with TAC, and if possible report back here if specific requests are needed.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Sep 14, 2021 06:29 PM
From: Zak Emerick
Subject: WLAN Northbound API is not enabled for customer id xxxx
This appears to still be an issue. I can call some APIs but not this one: /configuration/v1/wlan/{group_name_or_guid}/{wlan_name}
It seems I can't call anything under /configuration/* API is DEFINITELY enabled as I can call anything under the Monitoring node.
Does this node need special treatment from TAC?
------------------------------
ACCX #1239 || ACMX #1384 || ACEP || ACSP || CWNA || CWSP
Original Message:
Sent: Feb 25, 2021 03:20 PM
From: Herman Robers
Subject: WLAN Northbound API is not enabled for customer id xxxx
Looks like the API is disabled for your account. Open a TAC case and ask them to enable it, or check why it is not working.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
Original Message:
Sent: Feb 24, 2021 07:44 AM
From: Evgeny Tsirkin
Subject: WLAN Northbound API is not enabled for customer id xxxx
Having the same problem here
Getting
{
"description": "WLAN Northbound API is not enabled for customer id:.",
"error_code": "0001",
"service_name": "Configuration"
}
On any REST API call for WLAN Configuration
Is this a problem with being under evaluation, eventually?
Thanks
------------------------------
Evgeny Tsirkin
Original Message:
Sent: Nov 26, 2020 10:04 AM
From: travis schlafke
Subject: WLAN Northbound API is not enabled for customer id xxxx
Indeed its enabled. I am able to do some basic GETs and POST for new groups. Not sure why i get this error when then trying to create a WLAN. I haven't tried a ton of the endpoints yet. I sorta got stuck on this and was left scratching my head as to why this particular one doesn't work.
------------------------------
travis schlafke
Original Message:
Sent: Nov 26, 2020 03:24 AM
From: Herman Robers
Subject: WLAN Northbound API is not enabled for customer id xxxx
From the message, it looks like the API is simply not enabled. I assume that you did create an API Token for 'Network Operations' in the Account Home -> API Gateway screen? As far as I understand, API is enabled by default for all accounts, but not 100% sure if that applies to evaluation accounts.
Please reach out to Aruba support or your Aruba rep.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC.
Original Message:
Sent: Nov 25, 2020 07:07 PM
From: travis schlafke
Subject: WLAN Northbound API is not enabled for customer id xxxx
I'm having some issues with the Central API. I'm trying to create WLANs for my existing groups however I get a 400 error returned via both postman and swagger interface:
"description": "WLAN Northbound API is not enabled for customer id: xxxxxxxx.",
"error_code": "0001",
"service_name": "Configuration"
I can create groups...although I've had issues with my calls from postman at times but always works thru swagger...So I'm going to assume the issue lies more with postman rather than the actual POST I am trying to make.
I am on a demo trial at the moment, do I need to talk to my Aruba rep and get this turned on for my account or am I doing something wrong?