---
title: "Get all suppliers of the customer"
method: GET
path: "/public/v1/suppliers"
tags: ["Suppliers - Management"]
deprecated: true
---

# Get all suppliers of the customer

`GET /public/v1/suppliers`

> **Deprecated.**

⚠️ **DEPRECATED** - This endpoint is deprecated and will be removed at the end of December 2026.

---

## Migration Required

This endpoint has been replaced by the v2 Supplier Management API. Please migrate to the new endpoints:

### Replacement Endpoints

| Old Endpoint | New Endpoint | Purpose |
|--------------|--------------|---------|
| `GET /public/v1/suppliers` | `GET /public/v2/suppliers/sites` | List all suppliers |
| `GET /public/v1/target/prewave/{targetId}` | `GET /public/v2/suppliers/sites/find-by-identifier?prewaveId={targetId}` | Get detailed supplier by ID |

---

## Why Migrate?

The v2 API provides significant improvements:

### 1. Simplified Response Structure
- **v1**: Returns complex `PublicTargetDTO` with 30+ fields including nested objects (parents, industries, collections, etc.)
- **v2**: Returns `PublicSupplierV2DTO` with only essential fields:
  - `prewaveTargetId` (Int)
  - `name` (String)
  - `address` (String?)
  - `city` (String?)
  - `countryCode` (String?)
  - `supplierIds` (List<PublicSupplierIdentifierId>)

**Example v2 Response:**
```json
{
  "content": [
    {
      "prewaveTargetId": 102006215,
      "name": "Acme Corporation",
      "address": "123 Main St, Vienna, Austria",
      "city": "Vienna",
      "countryCode": "AT",
      "supplierIds": [
        {"id": "SUP-12345", "source": "SAP"}
      ]
    }
  ]
}
```

### 2. Better Documentation
- Comprehensive examples for all endpoints
- Detailed error response documentation
- Clear parameter descriptions
- Migration guidance and best practices

### 3. Improved Consistency
- Fixed alphabetical ordering (by name, then by ID) for deterministic pagination
- Consistent response structure across all endpoints
- Predictable behavior for integrations

### 4. Target ID Stability Guidance
- Clear documentation about when target IDs may change
- Best practices for synchronization
- Guidance on handling target merges

### 5. Full CRUD Operations
- `POST /public/v2/suppliers/sites` - Create suppliers
- `DELETE /public/v2/suppliers/sites` - Deactivate suppliers
- `GET /public/v2/suppliers/sites/pending` - Track pending creations

### 6. Better Performance
- Optimized database queries
- Reduced response payload size (typically 60-80% smaller)
- Faster response times

---

## Quick Migration Guide

### Step 1: Update List Endpoint
**Before:**
```http
GET /public/v1/suppliers?page=0&size=20
```

**After:**
```http
GET /public/v2/suppliers/sites?page=0&size=20
```

### Step 2: Update Response Parsing
**Before:** Parse complex `PublicTargetDTO` with nested structures

**After:** Parse simplified `PublicSupplierV2DTO` with flat structure

### Step 3: Understand Sites vs Site-Groups
⚠️ **Important**: The v2 endpoint returns **only sites** (physical locations), not site-groups.

- **v1**: Included both sites and site-groups
- **v2**: Includes only sites (physical locations with addresses)
- **Result**: Total count may be lower in v2

If you need site-group information, you may need to adjust your integration logic or contact support for guidance.

### Step 4: Get Detailed Information (if needed)
If you need detailed supplier information, use the v2 search endpoint:
```http
GET /public/v2/suppliers/sites/find-by-identifier?prewaveId={prewaveTargetId}
```

---

## Breaking Changes

1. **Response Structure**: The response structure is completely different. You'll need to update your response parsing logic.
2. **Field Names**: Some field names have changed (e.g., `id` → `prewaveTargetId`).
3. **Removed Fields**: Many fields from v1 are not available in the list endpoint (use the detail endpoint if needed).
4. **Query Parameters**: The `hasNumber` parameter is not available in v2. Filter by supplier identifiers in your application logic if needed.
5. **Sites vs Site-Groups**:
   - **v1**: Returns both **sites** (physical locations/branches with addresses) and **site-groups** (general company owners without specific addresses)
   - **v2**: Returns **only sites** (physical locations/branches with addresses). Site-groups are excluded
   - **Impact**: The total number of elements returned by v2 may be **lower** than v1 because site-groups are excluded
   - **Why**: The v2 API focuses on physical supplier locations (sites) which are more relevant for most integrations

---

**Required Permission**: `ACCESS_PUBLIC_SUPPLIERS`

**Performance Impact**: Medium

For detailed migration examples and API reference, see the v2 Supplier Management API documentation.

## Query parameters

- `hasNumber` boolean
- `pageable` Pageable, required
  - `page` integer
  - `size` integer
  - `sort` string[]

## Response `200`

OK

## Other responses

- `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.
- `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)