Palo Alto Networks Interconnect Throughput API

The Interconnect Throughput API from Palo Alto Networks — 1 operation(s) for interconnect throughput.

Operations 1

POST /mt/sp-interconnect/monitor/interconnects/throughput Get Throughput By Interconnect #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/palo-alto-networks-interconnect-throughput-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

palo-alto-networks-interconnect-throughput-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: SP Interconnect Monitor Interconnect Throughput API
  version: '1.0'
  description: "These APIs deliver real-time visibility and performance analytics for all configured interconnect \nresources through the monitoring plane. They allow network teams to track health, bandwidth throughput, \nand data transfer volumes at the edge to ensure optimal network security and reliability. \nAccess these metrics during routine audits or active troubleshooting to diagnose latency spikes or BGP session instability. \nBy applying time-based filters and histograms, you can generate detailed traffic trends and monitor IP pool consumption across your global infrastructure. Created on February 12, 2026. © 2026 Palo Alto Networks, Inc."
servers:
- url: https://api.sase.paloaltonetworks.com
security:
- authKey: []
tags:
- name: Interconnect Throughput
paths:
  /mt/sp-interconnect/monitor/interconnects/throughput:
    post:
      tags:
      - Interconnect Throughput
      summary: Get Throughput By Interconnect
      description: Monitor the real-time and historical throughput rates for designated Interconnect resources. This metric tracks the speed of data flow across the Service Provider bridge to identify potential bottlenecks or underutilized capacity. Access this when performing performance tuning or when investigating regional latency issues. To proceed, define the throughput properties and use the histogram object to group data by time intervals, such as daily or hourly trends.
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/MonitorRequest'
            example:
              properties:
              - property: egress_throughput
              - property: ingress_throughput
              - property: event_time
              - property: interconnect_name
              filter:
                operator: AND
                rules:
                - property: event_time
                  operator: last_n_days
                  values:
                  - 30
                - property: interconnect_id
                  operator: equals
                  values:
                  - c4ac1d7a-684e-11f0-92e9-4201ac16024e
              histogram:
                property: event_time
                range: day
                enableEmptyInterval: false
                value: '1'
      responses:
        '200':
          description: Success
          content:
            application/json:
              example:
                data:
                - egress_throughput: 0.002407656942160277
                  ingress_throughput: 0.004687820775191641
                  event_time: 1763424000000
                  interconnect_name: ic-us-central1
                - egress_throughput: 0.0024075402109722268
                  ingress_throughput: 0.0044653834247916635
                  event_time: 1763510400000
                  interconnect_name: ic-us-central1
                requestId: 3fb923a8-0077-443b-a334-07b3cd2123ed
        '400':
          description: Bad Request
        '401':
          description: Permission Denied
        '500':
          description: Server Error
      operationId: PostMtSp-interconnectMonitorInterconnectsThroughput
components:
  schemas:
    MonitorRequest:
      type: object
      properties:
        properties:
          type: array
          items:
            type: object
            properties:
              property:
                type: string
              function:
                type: string
              alias:
                type: string
              sort:
                type: object
                properties:
                  order:
                    type: string
        filter:
          type: object
          properties:
            operator:
              type: string
            rules:
              type: array
              items:
                type: object
                properties:
                  property:
                    type: string
                  operator:
                    type: string
                  values:
                    type: array
                    items: {}
        histogram:
          type: object
          properties:
            property:
              type: string
            range:
              type: string
            enableEmptyInterval:
              type: boolean
            value:
              type: string
  securitySchemes:
    authKey:
      type: http
      scheme: Bearer