Skip to main content
POST
/
transactions
/
{id}
/
assign
Assign transaction to account holder
curl --request POST \
  --url https://api.ledgerbeam.com/v1/transactions/{id}/assign \
  --header 'API-KEY: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "account_holder_id": "35b927b6-6fda-40aa-93b8-95b47c2b2cad"
}'
{
  "id": "ee02c3be-3825-449c-a35f-7b7cc47675e8",
  "account_holder_id": "35b927b6-6fda-40aa-93b8-95b47c2b2cad",
  "assigned_at": "2024-01-15T10:30:00Z",
  "status": "assigned"
}

​
Overview

Assign a transaction to a specific account holder. This endpoint allows you to associate transactions with account holders for better organization and analysis.
  • Transaction Organization: Assign transactions to specific account holders
  • Multi-User Systems: Distribute transactions among different users or departments
  • Account Management: Organize transactions by customer or account
  • Workflow Management: Assign transactions for processing or review

Authorizations

​
API-KEY
string
header
required

API key for authentication

Path Parameters

​
id
string
required

Transaction ID

Body

application/json
​
account_holder_id
string
required

Account holder ID to assign the transaction to

Example:

"35b927b6-6fda-40aa-93b8-95b47c2b2cad"

Response

Transaction assigned successfully

​
id
string

Transaction ID

Example:

"ee02c3be-3825-449c-a35f-7b7cc47675e8"

​
account_holder_id
string

Assigned account holder ID

Example:

"35b927b6-6fda-40aa-93b8-95b47c2b2cad"

​
assigned_at
string<date-time>

Assignment timestamp

Example:

"2024-01-15T10:30:00Z"

​
status
enum<string>

Assignment status

Available options:
assigned,
unassigned
Example:

"assigned"