---
title: "3. Send additional data"
method: POST
path: "/api/pvt/transactions/{transactionId}/additional-data"
tags: ["Transaction Process"]
---

# 3. Send additional data

`POST /api/pvt/transactions/{transactionId}/additional-data`

The third step to create a new transaction. This request sends additional data related to the transaction, such as profile information, shopping cart, shipping data, among others.

## Permissions

Any user or [application key](https://developers.vtex.com/docs/guides/api-authentication-using-application-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 | **Process payments** |

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 app keys](https://help.vtex.com/en/tutorial/best-practices-application-keys--7b6nD1VMHa49aI5brlOvJm) when assigning License Manager roles to integrations.

## Path parameters

- `transactionId` string, required

## Headers

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

## Request body

- object[] — Array containing additional data.
  - `name` string, required — Dataset name. This information must be sent in escaped JSON format.
  - `value` string, required — Dataset values. This information must be sent in escaped JSON format.

## Response `200`

OK. This endpoint does not return any data in the response body.

## Changes

- **2024-02-06** `f2ac9712d7ce` — 1 info
  - request body became optional
- **2024-01-22** `3e832ee956c6` — 1 breaking
  - the `items/value` request property type changed from `object` to `string`
- **2024-01-22** `6284eed6393b` — 1 breaking
  - the `items/name` request property type changed from `object` to `string`
- **2024-01-22** `dc85c7465125` — 2 breaking, 2 warning
  - added the new required request property `items/name`
  - added the new required request property `items/value`
  - removed the request property `items/clientProfileData`
  - removed the request property `items/shippingData`
- **2024-01-16** `5f4eed6283ef` — 1 info
  - the request property `items/shippingData/address/country` became nullable

[Full history](https://skmtc.dev/vtex/apis/payments-gateway-api/changes/api/pvt/transactions/:transactionId/additional-data/post.md)

---

[API](https://skmtc.dev/vtex/apis/payments-gateway-api.md) · [All operations](https://skmtc.dev/vtex/apis/payments-gateway-api/llms.txt) · [OpenAPI document](https://skmtc.dev/vtex/apis/payments-gateway-api/revisions/8c3eebc98efb?raw)