Many systems publish their data through a web API instead of a file. In Power Query, Web.Contents fetches the response and Json.Document turns the JSON into M values: an object becomes a record, an array becomes a list.
APIs usually wrap the rows in a field such as data: Source[data] is the list of records, and Table.FromRecords makes a row from each record and a column from each field. A field that holds another object, such as customer, arrives as a nested record. Table.ExpandRecordColumn turns its fields into columns and returns null where a record lacks a field, which is common when a field is optional.
Keep the base address fixed and pass the rest as options: Web.Contents(base, [RelativePath = "v2/tickets", Query = [status = "open"]]). The Power BI service can refresh that form on a schedule; an address glued together from text often can't. Large results come in pages, so read each page and combine the data lists with List.Combine.
In this practice editor the API responses are supplied with the exercise; a real call also needs credentials and a privacy level for the source.
The response becomes a table of tickets, and the nested customer record becomes two columns.