What is the API path to retrieve a balance transaction?

What is the API path to retrieve a balance transaction?

• A. GET v1/balance_transactions/:id
• B. GET v1/transactions/:id
• C. POST v1/balance_transactions
• D. GET v1/balance/:id

Answer: (A)

Retrieving a balance transaction uses a GET request on the specific balance transaction resource, with the transaction’s unique id in the URL. The proper path is /v1/balance_transactions/{id}. This follows the common REST pattern of fetching a single item by its identifier. Why this path fits: balance_transactions is the resource that represents individual balance operations, and appending the id selects one particular balance transaction. The GET method signals retrieval, not creation or listing. Why the other options don’t fit: using a different resource like transactions would refer to a different type of object, and the balance path targets a different endpoint. Using POST would imply creating a new balance transaction rather than fetching an existing one.

Retrieving a balance transaction uses a GET request on the specific balance transaction resource, with the transaction’s unique id in the URL. The proper path is /v1/balance_transactions/{id}. This follows the common REST pattern of fetching a single item by its identifier.

Why this path fits: balance_transactions is the resource that represents individual balance operations, and appending the id selects one particular balance transaction. The GET method signals retrieval, not creation or listing.

Why the other options don’t fit: using a different resource like transactions would refer to a different type of object, and the balance path targets a different endpoint. Using POST would imply creating a new balance transaction rather than fetching an existing one.