"
```
* Example Response:
{
"id": "fb6c9222-3204-4612-8ed7-8db516c6c715",
"status": "TO_SUBMIT",
"activityType": "EXPORT",
"countryOfActivity": "IT",
"customId": "DEC-24-238620",
"components": [
{
"commodity": "soya",
"ddsReference": {
"id": "24DKYIGLPU3439",
"verificationNumber": "4NAB3QYM"
}
}
]
// Note: Additional parameters may be returned in the response but are omitted here for brevity.
}
3. **Receiving a DDS Reference and Verification Number**
After a transaction is successfully submitted to TRACES, the system continuously checks for the assigned DDS reference and verification number. Since TRACES assigns these asynchronously, TradeAware automatically retrieves and updates them.
* Endpoint: `GET /transactions/{id}`
* Example Request:
curl -X GET https://api.tradeaware.live-eo.com/transactions/fb6c9222-3204-4612-8ed7-8db516c6c715 \
-H "Authorization: Bearer <token>"
DDS reference and verification numbers are returned once the transaction is **AVAILABLE**.
***
### **Use Case 4: Linking Transactional Data to Compliance Workflows (e.g., Batches, Shipments)**
**Business Case:**
Businesses need to link transactional data, such as batches, shipments, Purchase Orders etc. to compliance workflows to create a robust audit trail and maintain regulatory compliance. Without this linkage, inefficiencies and compliance risks can arise.
**Solution:**
Leverage the `customData` field in the Transactions API to associate SOs with POs for seamless traceability.
**Create a Batch linked to a purchase order:**
* Endpoint: `POST /transactions`
* Example Request:
```shellscript
curl -X POST https://api.tradeaware.live-eo.com/businesses/{businessId}/transactions \
-H "Authorization: Bearer " \
-H "Content-Type: application/json" \
-d '{
"activityType": "DOMESTIC",
"countryOfActivity": "US",
"components": [],
"customData": {
"transactionType": "Batch",
"linkedOrders": "PO001",
"salesRegion": "North America"
}
}'
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.live-eo.com/tradeaware/using-the-tradeaware-api/manage-your-transactions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.