How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Confluent Private Link Attachments (networking/v1) API

[![General Availability](https://img.shields.io/badge/Lifecycle%20Stage-General%20Availability-%2345c6e8)](#section/Versioning/API-Lifecycle-Policy)PrivateLink attachment objects represent reservations to establish PrivateLink connectionsto a cloud region in order to access resources that belong to a Confluent Cloud Environment.The API allows you to list, create, read update and delete your PrivateLink attachments.## The Private Link Attachments Model## Quotas and LimitsThis resource is subject to the [following quotas](https://docs.confluent.io/cloud/current/quotas/overview.html):| Quota | Description || --- | --- || `private_link_attachments_per_environment` | Number of PrivateLink Attachments per environment |

Confluent Private Link Attachments (networking/v1) API is one of 127 APIs that Confluent publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Private Link Attachments (networking/v1). The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 5 operations across 2 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://api.confluent.cloud.

5 operations 2 paths 17 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.confluent.cloud
Authentication
HTTP Basic, OAuth 2.0, HTTP Basic, HTTP Basic, OAuth 2.0, OAuth 2.0
Resource Areas
1

Authentication & Security 6

Confluent Private Link Attachments (networking/v1) API declares 6 security schemes for authenticating requests. It accepts HTTP basic authentication (cloud-api-key). It supports OAuth 2.0 (confluent-sts-access-token) using the clientCredentials flow. It accepts HTTP basic authentication (global-api-key). It accepts HTTP basic authentication (resource-api-key). It supports OAuth 2.0 (external-access-token) using the clientCredentials flow. It supports OAuth 2.0 (oauth) using the clientCredentials flow, exposing 4 scopes.

  • cloud-api-key — Authenticate with Cloud API Keys using HTTP Basic Auth. Treat the Cloud API Key ID as the username and Cloud API Key Secret as the password.
  • confluent-sts-access-token — Authenticate with Confluent API using this credentials (JSON Web Tokens) following OAuth 2.0.
  • global-api-key — Authenticate with Global API Keys using HTTP Basic Auth. Treat the Global API Key ID as the username and Global API Key Secret as the password.
  • resource-api-key — Authenticate with resource-specific API Keys using HTTP Basic Auth. Treat the resource-specific API Key ID as the username and resource-specific API Key Secret…
  • external-access-token — Authenticate with Confluent API using this credentials (JSON Web Tokens) following OAuth 2.0.
  • oauth — Authenticate with OAuth 2.0. Currently this is only supported for partner APIs.

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Private Link Attachments (networking/v1) 5

[![General Availability](https://img.shields.io/badge/Lifecycle%20Stage-General%20Availability-%2345c6e8)](section/Versioning/API-Lifecycle-Policy) PrivateLink attachment objects…

GET
/networking/v1/private-link-attachments
List of Private Link Attachments
listNetworkingV1PrivateLinkAttachments 7 params → 200400401403429500
POST
/networking/v1/private-link-attachments
Create a Private Link Attachment
createNetworkingV1PrivateLinkAttachment body → 202400401402403409422429
GET
/networking/v1/private-link-attachments/{id}
Read a Private Link Attachment
getNetworkingV1PrivateLinkAttachment 2 params → 200400401403404429500
PATCH
/networking/v1/private-link-attachments/{id}
Update a Private Link Attachment
updateNetworkingV1PrivateLinkAttachment 1 param body → 200400401402403404409422
DELETE
/networking/v1/private-link-attachments/{id}
Delete a Private Link Attachment
deleteNetworkingV1PrivateLinkAttachment 2 params → 204400401403404429500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are Error (8 properties), networking.v1.PrivateLinkAttachment (6 properties), ObjectReference (6 properties), ObjectMeta (5 properties). Each schema is shown below with its type and property counts.

ObjectMeta
object
ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create.
5 properties 1 required
networking.v1.GcpPscServiceAttachment
object
GCP PSC Service attachment with reserved capacity to connect a PSC Endpoint.
1 property 1 required
MultipleSearchFilter
array
Filter a collection by a string search for one or more values
networking.v1.AzurePrivateLinkService
object
Azure Private Link Service with reserved capacity to connect a Private Endpoint.
2 properties 2 required
ListMeta
object
ListMeta describes metadata that resource collections may have
5 properties
networking.v1.AzurePrivateLinkAttachmentStatus
object
Azure PrivateLink attachment represents reserved capacity in a PrivateLink service that can be used to establish PrivateLink
2 properties 2 required
networking.v1.PrivateLinkAttachmentList
object
PrivateLink attachment objects represent reservations to establish PrivateLink connections to a cloud region in order to access resources that belong to a Conf…
4 properties 4 required
ObjectReference
object
ObjectReference provides information for you to locate the referred object
6 properties 3 required
networking.v1.AwsPrivateLinkAttachmentStatus
object
AWS PrivateLink attachment represents reserved capacity in an AWS VPC Endpoint Service that can be used to establish PrivateLink connections.
2 properties 2 required
SearchFilter
string
Filter a collection by a string search
networking.v1.PrivateLinkAttachmentSpec
object
The desired state of the Private Link Attachment
4 properties
networking.v1.PrivateLinkAttachment
object
PrivateLink attachment objects represent reservations to establish PrivateLink connections to a cloud region in order to access resources that belong to a Conf…
6 properties
networking.v1.GcpPrivateLinkAttachmentStatus
object
GCP PrivateLink attachment represents reserved capacity in a GCP PSC Service attachment. A PSC Endpoint can be connected to the Service attachment.
2 properties 2 required
networking.v1.AwsVpcEndpointService
object
AWS VPC Endpoint service that can be used to create VPC Endpoints.
1 property 1 required
Error
object
Describes a particular error encountered while performing an operation.
8 properties
Failure
object
Provides information about problems encountered while performing an operation.
1 property 1 required
networking.v1.PrivateLinkAttachmentStatus
object
The status of the Private Link Attachment
5 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

confluent-private-link-attachments-networking-v1-api-openapi.yml Raw ↑

Other APIs Confluent publishes across the network.

Confluent
Confluent Managed MCP Servers
Confluent ACLs API
Confluent API Keys API
Confluent Clusters API
Confluent Consumer Groups API
Confluent Environments API
Confluent Partitions API
Confluent Service Accounts API
Confluent Topics API
Confluent Access Points (networking/v1) API
Confluent ACL (v3) API
Where this information came from

This is an independent, third-party profile of Confluent Private Link Attachments (networking/v1) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.