Skip to content

feat(customer): add singular customer key on GET /v1/customer/:id #292

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CryptoJones merged 1 commit into from
May 19, 2026
Merged

feat(customer): add singular customer key on GET /v1/customer/:id #292

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions app/controllers/customercontroller.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -560,8 +560,16 @@ async function findAndRespond(customerId, res) {
// customers — soft-deletes correctly surface as 404 too.
return res.status(404).json({ message: "Not found." });
}
// The historical key is `customers` (plural) wrapping a single
// customer — a wart from before the codebase standardized on
// singular-for-single-row across the other 15 entities. Add
// the consistent `customer` key alongside it so SDK clients
// can read the same shape they get from /v1/worker/:id et al.
// The `customers` key stays for backward compat; remove in a
// future major version.
return res.status(200).json({
message: "Successfully retrieved the customer with CustomerId " + customerId,
customer,
customers: customer,
});
} catch (error) {
Expand Down