receipt form api endpoints

[sunb26]

Receipts (Expenses)

1. Save image capture
2. Save inference result
3. Create new snapshot(s)

@Zack-Ren please add more endpoints if I missed any or new ones come up!

[zackxzr]

[POST] /get-receipts/{userId}?limit=X&offset=Y
(We can also use request body instead of query string)

• returns list of receipts associated with userId

[Lev1ty]

what about the following instead?

GET /users/{userId}/receipts?limit=X&offset=Y

[zackxzr]

Yeah that works, I like that.

[sunb26]

@Lev1ty What is the reason for switching to query string params instead of keeping everything in the request body? All of the other endpoints at this point have been part of the request body so I'm thinking we keep it consistent if possible.

[Lev1ty]

1. GET requests do not have bodies
2. GET are more amenable to caching
3. POST does not make sense semantically as the HTTP verb here, since we are not going with rpc-json
4. limit and offset are typical query params and this pattern is common, though a more performant alternative is using a pagination token, as offset is always a linear scan on DB whereas can retrieve page token (an id in the db) if it is indexed in log complexity @Zack-Ren

[zackxzr]

If we want to include a searching feature where we can filter by a search parameter and query, we could use POST and pass the search parameters in the body. For now, what @Lev1ty mentioned in 4 above is sufficient imo.