---
title: "Create connection contact for a supplier by identifier"
method: POST
path: "/public/v2/suppliers/connection-contacts"
tags: ["Suppliers - Connection Contacts"]
---

# Create connection contact for a supplier by identifier

`POST /public/v2/suppliers/connection-contacts`

### Overview
Create a new connection contact for a supplier identified by any of its identifiers (supplierId, customerId, ownId, or prewaveId).

This endpoint allows you to add contact persons to suppliers for relationship management. If your organization is not yet connected to the identified target, it will be automatically connected as a supplier.

### Auto-Connection Logic
- If the identified target is not yet connected to your organization, an edge of type 'Supplier' will be created automatically.
- This requires the additional internal permission `access_public_mng_customer_conn`.

### Related Operations
- **List Contacts**: [GET /public/v2/suppliers/connection-contacts](#operations-Suppliers_-_Connection_Contacts-findConnectionContactsByIdentifier)
- **Delete Contact**: [DELETE /public/v2/suppliers/connection-contacts/{contactId}](#operations-Suppliers_-_Connection_Contacts-deleteConnectionContact)

### Required Permission
`access_public_suppliers` and `access_public_mng_conn_contacts`

## Query parameters

- `supplierId` string
- `customerId` string
- `ownId` string
- `prewaveId` integer
- `source` string

## Request body

- PublicConnectionContactPayload — Payload for creating or updating a connection contact. Contains the contact's email address.
  - `email` string, email, required — Email address of the connection contact.

## Response `201`

Connection contact created successfully

- PublicSupplierConnectionContact — Public representation of a supplier's connection contact. Contains the unique contact ID and the contact's email address.
  - `id` integer, required — Unique identifier of the connection contact.
  - `email` string, email, nullable — Email address of the connection contact. May be null if not provided.

## Other responses

- `400` — 400 Bad Request - Invalid request, multiple suppliers found, or target not connectable.
- `403` — 403 Forbidden - Authentication or authorization failure. This status code is returned when: (1) the request lacks valid authentication credentials (missing or invalid X-Auth-Token header), or (2) the authenticated user does not have the required permission to access this resource.
- `404` — 404 Not Found - Supplier not found
- `429` — 429 Too Many Requests - API rate limit exceeded. The request has been rejected because the rate limit for this endpoint has been exceeded. Default rate limits: GET requests - 100 per 10 seconds, 500 per minute; POST/PUT/PATCH/DELETE requests - 20 per 10 seconds, 100 per minute. For increased access, please contact customer success.
- `500` — 500 Internal Server Error - An unexpected error occurred on the server. The request may or may not have been processed.

---

[API](https://skmtc.net/prewave/apis/public-prewave-api.md) · [All operations](https://skmtc.net/prewave/apis/public-prewave-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/prewave/public-prewave-api/revisions/466169815b78/schema)