From what I read, you can create the profile, but not assign it. Correct?
What is the payload you try to send to assign the policy?
Here is a scope-map payload that works for me:
{
"scope-map": [
{
"scope-name": "81316374940000256",
"persona": "ACCESS_SWITCH",
"resource": "layer2-vlan/1234"
}
]
}
You should use the scope id for global, which I get from a profile already assigned to global; but there probably are smarter ways to do i.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
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: Feb 18, 2026 03:39 PM
From: chris.discianno
Subject: New Central Portal API
I've been trying to create configuration profiles (like vrfs) using API. I've gotten the creation of the profile, but I can't seem to get API to a device type (CORE_SWITCH) and scope (GLOBAL). I've looked at the API documentation, but no matter what I try for the POST, it keeps coming back with a bad payload. Does anyone have any experience getting config-assignment working through API. I've been trying it with Python and even with Postman. Any help would be greatly appreciated.
-------------------------------------------