# Creates Third Party Codes

{% partial file="snips/post-tpcd-description.md" /%}

Endpoint: POST /interfaces/thirdPartyCodes
Version: v3.0: 3.26.2.2
Security: Auth API User Token

## Query parameters:

  - `suppressOutput` (boolean)

## Request fields (application/json-patch+json):

  - `id` (string)
    A unique identifier for the TPCode Record
            
This is autogenerated by Yellow Dog on creation of the record.

  - `type` (string, required)
    The Type of code being entered. This should be titled specifically for the third party integrator in Pascal case.
            
A common way to type specifically is to prepend the Type with the name of the integration.

This will be displayed in the Interfaces tab under the Accounting/Other section as "Integration Name Tax Grouping"

  - `code` (string, required)
    Identifier used by the Integrator to match certain behavior on their side of the integration.

  - `description` (string, required)
    User friendly description that will be displayed to the user as part of a drop down box titled by the type

  - `store` (object)

  - `store.id` (string)

## Response 201 fields (application/json):

  - `id` (string)
    A unique identifier for the TPCode Record
            
This is autogenerated by Yellow Dog on creation of the record.

  - `type` (string, required)
    The Type of code being entered. This should be titled specifically for the third party integrator in Pascal case.
            
A common way to type specifically is to prepend the Type with the name of the integration.

This will be displayed in the Interfaces tab under the Accounting/Other section as "Integration Name Tax Grouping"

  - `code` (string, required)
    Identifier used by the Integrator to match certain behavior on their side of the integration.

  - `description` (string, required)
    User friendly description that will be displayed to the user as part of a drop down box titled by the type

  - `store` (object)

  - `store.id` (string)

  - `store.code` (string,null)

  - `store.name` (string,null)

## Response 400 fields (application/json):

  - `type` (string,null)

  - `title` (string,null)

  - `status` (integer,null)

  - `detail` (string,null)

  - `instance` (string,null)

## Response 500 fields (application/json):

  - `message` (string,null)

  - `errors` (array,null)

  - `errors.extensions` (string,null)


## Response 200 fields

## Response 429 fields