Required headers in Meraki API
Content: application/json
X-Cisco-Meraki-API-Key: <apikey>
POST https://{vmanage-ip-address}/j_security_check Content-Type: application/x-www-form-urlencoded HTTP Body: "j_username={admin}&j_password={credential}
GET https://{vmanage-ip-address}/dataservice/client/token Content-Type: application/json HTTP Header: "Cookie: JESSIONID={session hash id}"
https://{vmanage-ip-address}/dataservice/{api-endpoint-url} Content-Type: application/json HTTP Header: "Cookie: JESSIONID={session hash id}" "X-XSRF-TOKEN: {XSRF token}"
USC Manager Northbound Protocol - RPC XML-API
Northbound Protocol - REST API
Overview: PLatform for UCS/Hyperflex management to streamline management with agile. Provides health dashboards for all UCS/Hyperflex. Provides vKVMS, RESTful API, policy and firmware upgrades.
It uses a device connector in the software to connect to their SaaS platform.
Northbound Protocol - REST API
Overview: The point of UCS manager is to remove the complexity by introducing fabric interconnect that have intelligence.
Service Profile resides on interconnects they can contain mac addresses, BIOS options, firmware and Universal Unique IDentifier (UUID) that be applied to specific blades.
Benefits:
- Flexibility
- Less disruption
- ease of management
- Lower OPex/CAPex
Cisco ACI - N9k
Northbound Protocol - REST API
ACI Fabric managed by APIC
Centralized Management and control
Policy Enforcement
Automated Fabric Provisioning
Webex Devices Northbound - RESTAPI
UCM UDS - REST API
AXL - XML/SOAP
Finesse Call Manager REST-API(xml)
Webex Teams Messaging/calling REST-API (JSON)