Network Management API

Name: Network Management API API
Brand: Network Management API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingoauth214 EndpointsREST

For Agents

Run Google Cloud connectivity tests across VPCs and hybrid networks. Use to verify reachability after network changes or during incident response.

Quickstart

Get started with Network Management API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"run a Google Cloud connectivity test between two VPC instances"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Network Management API API.

Create a connectivity test between source and destination endpoints

Rerun an existing connectivity test to refresh its results

List all connectivity tests in a project and location

Inspect detailed reachability traces showing each network hop

GET STARTED

Start building with Network Management API API

Explore with Jentic

View OpenAPI Document

Use for: Create a connectivity test between two VPC subnets, Rerun a failing connectivity test after a firewall change, List all connectivity tests in a project, Get the trace for the latest run of a test

Not supported: Does not modify firewall rules, routes, or live traffic — use for Google Cloud reachability and connectivity diagnostics only.

The Network Management API provides Google Cloud's network performance monitoring and diagnostics surface. It exposes connectivityTests as a primary resource — a saved test definition with source and destination endpoints — together with operations for create, list, rerun, and delete. Use it to verify reachability across VPCs, hybrid networks, and Network Connectivity Center hubs as part of change management or incident response.

Use Cases

Patterns agents use Network Management API API for, with concrete tasks.

★ Pre-Change Reachability Verification

Before merging firewall or routing changes, platform teams run a saved suite of connectivity tests to confirm critical paths still work. The connectivityTests resource accepts source and destination endpoints by IP, instance, GKE cluster, or Cloud SQL instance, and returns a per-hop reachability trace for each test.

POST /v1/{parent}/connectivityTests with source.instance and destination.instance set, then POLL the operation until reachabilityDetails.result is REACHABLE.

Incident Response Trace

When a service reports timeouts, on-call engineers create or rerun a connectivity test from the affected workload to its dependencies. The returned trace shows where packets are dropped — firewall rule, route, or peering — turning a vague 'network issue' into a specific config to fix.

POST /v1/{name}:rerun, then GET /v1/{name} and inspect reachabilityDetails.traces to identify the failing step.

Hybrid Path Validation

After standing up a Network Connectivity Center hub or new VPN tunnel, hybrid teams validate reachability between on-premises CIDRs and cloud workloads. Connectivity tests support endpoints described by raw IP plus network, so the same test definition can compare expected versus observed reachability across an entire hybrid topology.

POST /v1/{parent}/connectivityTests with source.ipAddress (on-prem) and destination.instance (in-cloud), then surface trace steps that mention the VPN tunnel or hub.

AI Agent Network Diagnostician

An AI agent reachable through Jentic owns post-change validation: when a deployment changes networking, the agent reruns the relevant connectivity tests and posts the trace summary back to the change ticket. Jentic isolates OAuth credentials and exposes the right Network Management operation per intent so the agent never sees Google service account keys.

Search Jentic for 'rerun a Google Cloud connectivity test', load projects.locations.global.connectivityTests.rerun, and execute with the test resource name.

Key Endpoints

14 endpoints — the network management api provides google cloud's network performance monitoring and diagnostics surface.

METHOD

PATH

DESCRIPTION

GET

/v1/{parent}/connectivityTests

List connectivity tests in a project and location

POST

/v1/{parent}/connectivityTests

Create a connectivity test

PATCH

/v1/{name}

Update a connectivity test

DELETE

/v1/{name}

Delete a connectivity test

POST

/v1/{name}:rerun

Rerun an existing connectivity test

POST

/v1/{name}:cancel

Cancel a long-running operation

GET

/v1/{parent}/connectivityTests

List connectivity tests in a project and location

POST

/v1/{parent}/connectivityTests

Create a connectivity test

PATCH

/v1/{name}

Update a connectivity test

DELETE

/v1/{name}

Delete a connectivity test

POST

/v1/{name}:rerun

Rerun an existing connectivity test

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

OAuth 2.0 refresh tokens are stored encrypted in the Jentic vault. The agent receives scoped, short-lived access tokens — Google Cloud service account keys never enter the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'rerun a Google Cloud connectivity test') and Jentic returns the matching Network Management operation with its input schema.

Time to first call

Direct integration: 1-3 days for OAuth, IAM, and operation polling. Through Jentic: under an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Compute Engine API

Manages the VPCs, instances, and firewall rules whose reachability you test

Use Compute Engine to fix the firewall or route a connectivity test trace flagged as the failing hop.

Complementary

Network Connectivity API

Builds the hub-and-spoke topology whose reachability you validate

After standing up a Network Connectivity Center hub, run Network Management connectivity tests across the new spokes.

Complementary

Network Security API

Manages firewall and security policies that often appear as failing hops

When a connectivity test trace points at a firewall, use Network Security to inspect or amend the offending policy.

Complementary

Cloud DNS API

Resolves the names whose IPs are tested for reachability

Use Cloud DNS to confirm DNS records before running a connectivity test against the resolved IP.

FAQs

Specific to using Network Management API API through Jentic.

What authentication does the Network Management API use?

OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope (Oauth2 securitySchemes are declared in the spec). The caller needs networkmanagement IAM roles on the project. Jentic stores OAuth refresh tokens in MAXsystem and exposes only short-lived access tokens to the agent.

Which endpoint types can a connectivity test target?

Source and destination endpoints accept IP address, GCE instance, GKE cluster master, Cloud SQL instance, App Engine version, Cloud Run service, and Cloud Function. Each type is set on the endpoint object in the connectivity test body.

What are the rate limits for the Network Management API?

Per-project quotas are listed in Cloud Console under IAM and Admin > Quotas. Test runs are long-running operations; pace creates and reruns by polling the operation and backing off on 429 with exponential backoff.

How do I rerun a connectivity test through Jentic?

Search Jentic for 'rerun a Google Cloud connectivity test', load projects.locations.global.connectivityTests.rerun, and execute with the test resource name. Jentic refreshes OAuth in the background and surfaces the long-running operation name.

Does this API drop or change packets in production?

No. Connectivity tests perform passive reachability analysis using configuration, not live traffic. They do not modify firewall rules, routes, or workloads — they only return the configured-state trace and verdict.