You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 26, 2022. It is now read-only.
We need to support searching all Customer records stored in the database. This allows the UI and other programs to find records. Creating transfers can occur well after the initial creation and UI's / services will need to relocate the correct customerID to use.
Initially I'm thinking of the following endpoint with a bunch of query params. GET /customers
?name=<string> (optional) used and split across first/last names, returns fuzzy results
?email=<string> (optional) exact match (with .'s removed)
?type=<string> (optional) individual and business filter
We need to support searching all
Customer
records stored in the database. This allows the UI and other programs to find records. Creating transfers can occur well after the initial creation and UI's / services will need to relocate the correctcustomerID
to use.Initially I'm thinking of the following endpoint with a bunch of query params.
GET /customers
?name=<string>
(optional) used and split across first/last names, returns fuzzy results?email=<string>
(optional) exact match (with.
's removed)?type=<string>
(optional)individual
andbusiness
filterThoughts @InfernoJJ and @joshsadler ?
The text was updated successfully, but these errors were encountered: