---
title: "POST /partnerships/{partnershipId}/transaction-groups/{transactionGroupId}/transactions/{transactionSettingId}"
method: POST
path: "/partnerships/{partnershipId}/transaction-groups/{transactionGroupId}/transactions/{transactionSettingId}"
---

# POST /partnerships/{partnershipId}/transaction-groups/{transactionGroupId}/transactions/{transactionSettingId}

`POST /partnerships/{partnershipId}/transaction-groups/{transactionGroupId}/transactions/{transactionSettingId}`

This endpoint stages a transaction for outbound delivery.

## Path parameters

- `partnershipId` string, required — A unique ID for this partnership within Stedi. You can find this ID on the [Trading partners](https://www.stedi.com/app/core/partnerships) page under **Partnership identifier**.
- `transactionSettingId` string, required — A unique ID for the outbound transaction setting Stedi should use to determine the correct guide for validation and generation. It must be attached to the partnership associated with the `partnershipId`. To find the `transactionSettingsId`, go to the partnership and use the **Transaction Setting ID** field for the outbound transaction setting.
- `transactionGroupId` string, required — A unique ID for a group of transactions on Stedi. Stedi creates a new transaction group if one does not exist with the specified ID.

## Headers

- `Idempotency-Key` string — A unique string to identify this request to the server. The key can be up to 255 characters. You can safely retry requests with the same idempotency key within 24 hours of making the first request. This prevents sending duplicate data to your trading partners in case of network errors or other intermittent failures. Required if providing `async: true` [Learn more](https://www.stedi.com/docs/api-reference/index#idempotency-keys).

## Request body

- CreateTransactionGroupRequestContent
  - `transaction` unknown
  - `mappingId` string — Specify a mapping id to transform the transaction to Stedi's Guide JSON format. Can not be used with async: true.
  - `groupOverrides` TransactionGroupOverrides — Customize the Application IDs for you or your trading partner.
    - `localApplicationId` string — Set the [GS-02](https://www.stedi.com/edi/x12/segment/GS#GS-02) element to a custom value. If not set, Stedi uses the Application ID for the local profile associated with the partnership.
    - `partnerApplicationId` string — Set the [GS-03](https://www.stedi.com/edi/x12/segment/GS#GS-03) element to a custom value. If not set, Stedi uses the Application ID for the partner profile associated with the partnership.
  - `async` boolean — Determines if the transaction should be uploaded asynchronously through a presigned url. Either `transaction` or `async: true` is required. Idempotency-Key header is required when using async: true.

## Response `201`

CreateTransactionGroup 201 response

- CreateTransactionGroupResponseContent
  - `transactionGroupId` string, required — The transaction group ID where you created and added the transaction.
  - `createdAt` string, date-time, required — The time Stedi staged the transaction.
  - `transactionId` string, required — A unique ID for the staged transaction Stedi created within the group.
  - `uploadUrl` string — A pre-signed URL to upload the file using a `PUT` request.

## Other responses

- `400` — BadRequestException 400 response
- `401` — UnauthorizedException 401 response
- `403` — AccessDeniedException 403 response
- `404` — ResourceNotFoundException 404 response
- `409` — ResourceUnderChangeException 409 response
- `422` — UnprocessableEntityException 422 response
- `429` — ThrottlingException 429 response
- `500` — ServiceException 500 response
- `503` — ServiceUnavailableException 503 response
- `504` — GatewayTimeoutException 504 response

---

[API](https://skmtc.net/stedi/apis/core.md) · [All operations](https://skmtc.net/stedi/apis/core/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/stedi/core/versions/172bd33e0d66/schema)