Post ArWCbL56m0RKvWZYDA by mattmedeiros@podcastindex.social
 (DIR) More posts by mattmedeiros@podcastindex.social
 (DIR) Post #ArW8MwbWaAcB8pcDXE by dave@podcastindex.social
       2025-02-26T17:28:38Z
       
       0 likes, 0 repeats
       
       REST api question.  If I want a resource to be addressable in two different ways, is there a standard for overloading the definition?  Example:Read podcast info by ID:    GET /api/v2/podcast/920666Read podcast info by URL:    GET /api/v2/podcast/http%3A%2F%2Fmp3s.nashownotes.com%2Fpc20rss.xmlThese are the same underlying resource.  I just want them to be readable by either ID or URL since both are unique keys in the DB on that table.
       
 (DIR) Post #ArWCbL56m0RKvWZYDA by mattmedeiros@podcastindex.social
       2025-02-26T18:16:03Z
       
       0 likes, 0 repeats
       
       @dave https://claude.ai/share/6601b968-485a-47e7-b350-b9c3932fdf02(don't kill me for that LOL)
       
 (DIR) Post #ArWRqUhWmwfkPyEAAy by dave@podcastindex.social
       2025-02-26T21:06:49Z
       
       0 likes, 0 repeats
       
       @mattmedeiros Answered my question.  Approach 1 seems good. 🙏 Interesting that Claude didn't give any references.  Is that the new 3.7 model?
       
 (DIR) Post #ArWTEqyJjnM6OTGAfQ by mattmedeiros@podcastindex.social
       2025-02-26T21:22:26Z
       
       0 likes, 0 repeats
       
       @dave it is.
       
 (DIR) Post #Arb9rEzV8tcY0YPsYK by theDanielJLewis@podcastindex.social
       2025-03-01T03:38:51Z
       
       0 likes, 0 repeats
       
       @dave @mattmedeiros I was going to suggest #1 as well, or here's a #4: offer a separate "lookup" endpoint for things like the feed URL or Apple Podcasts ID that must be looked up and aren't a direct match like the PI ID number. GUID might need to be a lookup, too.
       
 (DIR) Post #ArbCvMOtpqZA0dx65Q by theDanielJLewis@podcastindex.social
       2025-03-01T03:40:48Z
       
       0 likes, 0 repeats
       
       @dave @mattmedeiros GET /api/v2/podcasts/920666GET /api/v2/podcasts/lookup?feedUrl=…GET /api/v2/podcasts/lookup?guid=…GET /api/v2/podcasts/lookup?apId=…Aside: I suggest using "podcasts" instead of "podcast" as most endpoints maintain that plural option in the hierarchy.
       
 (DIR) Post #ArbCvNeXBCfNtQH65w by dave@podcastindex.social
       2025-03-01T04:13:13Z
       
       0 likes, 0 repeats
       
       @theDanielJLewis @mattmedeiros 🙏