# Retrieve Counterparty Retrieves a list of counterparties given the filter parameters provided Endpoint: GET /v1/counterparties/{counterparty_id} Version: 1.1.2 Security: OAuth2Flow ## Path parameters: - `id` (string, required) Counterparty ID ## Header parameters: - `Authorization` (string) OAuth bearer token (see authentication flows) - `x-l2f-request-id` (string) Optional Unique ID per request, useful for fault resolution/diagnosis and audit. - `x-l2f-idempotency-id` (string) Unique ID used to safely retry an operation. See idempotency section for more details. ## Response 200 fields (application/json): - `data` (object, required) - `data.id` (string) Unique Identifier for the counter party - `data.customer_id` (string, required) The customer to which this counter party will be registered for use. - `data.description` (string) Description of the counterparty. - `data.counterparty_type` (string, required) The type of counterparty will determine the available rails for sending or receiving funds. See the guides for more detailed explanation of counterparty types. Enum: "FIAT_US", "FIAT_US_LINKED", "FIAT_CA", "FIAT_CA_LINKED", "CRYPTO" - `data.status` (string, required) Counterparty status determines options available for use on the counterparty. * ACTIVE - Counterparty is open and available for use for withdrawal or deposits * CLOSED - Counterparty is permanently closed, no further actions can be performed on the Counterparty. * PENDING - Counterparty is under additional review prior to moving to the OPEN or CLOSED state. No actions can be performed on the Counterparty in this state * FROZEN - Counterparty has been temporarily locked for all actions. * EDD - Counterparty requires enhanced due diligence to be performed. The counterparty will operate as if active but may transition to FROZEN or CLOSED post due-diligence. * DORMANT - No activity has been seen in the last 12 months. The counterparty is available for use. Enum: "ACTIVE", "CLOSED", "FROZEN", "PENDING", "EDD", "DORMANT" ## Response 400 fields (application/json): - `errors` (array) Error List - `errors.code` (string) Layer2 Standard Error Code - `errors.description` (string) Error Description ## Response 401 fields (application/json): - `errors` (array) Error List - `errors.code` (string) Layer2 Standard Error Code - `errors.description` (string) Error Description ## Response 404 fields (application/json): - `errors` (array) Error List - `errors.code` (string) Layer2 Standard Error Code - `errors.description` (string) Error Description ## Response 500 fields (application/json): - `errors` (array) Error List - `errors.code` (string) Layer2 Standard Error Code - `errors.description` (string) Error Description