---
title: "List all affiliations"
method: GET
path: "/api/pvt/affiliations"
tags: ["Configuration"]
---

# List all affiliations

`GET /api/pvt/affiliations`

Returns all affiliations (payment and anti-fraud providers) that are already configured in your store.

## Permissions

Any user or [API key](https://developers.vtex.com/docs/guides/api-authentication-using-api-keys) must have at least one of the appropriate [License Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) to be able to successfully run this request. Otherwise they will receive a status code `403` error. These are the applicable resources for this endpoint:

| **Product** | **Category** | **Resource** |
| --------------- | ----------------- | ----------------- |
| PCI Gateway | Payment-Make Payments | **View Payment Data** |

There are no applicable [predefined roles](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy) for this resource list. You must [create a custom role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role) and add at least one of the resources above in order to use this endpoint. To learn more about machine authentication at VTEX, see [Authentication overview](https://developers.vtex.com/docs/guides/authentication).

>❗ To prevent integrations from having excessive permissions, consider the [best practices for managing API keys](https://help.vtex.com/en/tutorial/best-practices-api-keys--7b6nD1VMHa49aI5brlOvJm) when assigning License Manager roles to integrations.

## Headers

- `Content-Type` string, required
- `Accept` string, required

## Response `200`

OK

- object[]
  - `id` string — Provider identification.
  - `implementation` string — Provider implementation class name.
  - `name` string — Provider name.
  - `configuration` object[] — Array containing configuration information fields.
    - `name` string, required — Configuration parameter name.
    - `value` string, nullable, required — Configuration parameter value.
    - `valueKey` string, nullable, required — Value key information.
  - `isdelivered` boolean — Indicates whether the provider is published and available for use.
  - `isConfigured` boolean — Indicates whether the provider is configured.

---

[API](https://skmtc.net/vtex/apis/payments-gateway-api.md) · [All operations](https://skmtc.net/vtex/apis/payments-gateway-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/vtex/payments-gateway-api/revisions/7f58d8045a19/schema)