v2 GET Receipts

[marfavi]

Right now, the app uses two API v1 calls to retrieve all user receipts:

• GET Tickets (used: true)
• GET Purchases

I propose a new GET Receipts endpoint to retrieve all receipts data through one endpoint. On the app side, it would mean reduced complexity (one less type to parse) and increased performance (one less API call).

[marfavi]

schema suggestion: list of ReceiptResponse

      "ReceiptResponse": {
        "type": "object",
        "description": "Representing a receipt for either a swipe or a purchase",
        "additionalProperties": false,
        "required": [
          "id",
          "productName",
          "type"
          "time",
        ],
        "properties": {
          "id": {
            "type": "integer",
            "description": "Id of swipe or purchase",
            "format": "int32",
            "example": 122
          },
          "time": {
            "type": "string",
            "description": "Time of swipe/purchase in Utc format",
            "format": "date-time",
            "minLength": 1,
            "example": "2022-01-09T21:03:52.2283208Z"
          },
          "productName": {
            "type": "string",
            "description": "Name of product a receipt is for",
            "minLength": 1,
            "example": "Fancy Coffee"
          },
          "type": {
            "description": "What type (swipe/purchase) the receipt represents",
            "example": "Purchase",
            "oneOf": [
              {
                "$ref": "#/components/schemas/ReceiptType"
              }
            ]
          }
        }
      }

[jonasanker]

I think we had this discussion previously. Maybe we can see if we can find the history for why we didn't go this way.

Also to understand the performance problem, do you know what each API call takes? Maybe there's a bottle neck in one of them.