# Create Counterparty

Create a new counterparty for the purpose of pulling funds into the platform or pushing out

Endpoint: POST /v1/counterparties
Version: 1.1.2
Security: OAuth2Flow

## 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.

## Request fields (application/json):

  - `customer_id` (string, required)
    The customer to which this counter party will be registered for use.

  - `description` (string)
    Description of the counterparty.

  - `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"

## Response 200 fields (application/json):

  - `data` (object, required)

  - `data.id` (string)
    Unique Identifier for the counter party

## 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