Structured JSON response from GET operation #53
Description
🤔 What's the problem you're trying to solve?
If a tool has made a GET request to kick off a publishing process, the end user URL is part of the terminal-formatted message in the response, and if you want to do something with that you have to parse it out of there.
✨ What's your proposed solution?
Make a backwards-compatible change to the API, so with an Accept: application/json header you get a structured JSON response that includes the message but also the URL as its own field.
⛏ Have you considered any alternatives or workarounds?
A custom header would also work, but I like this better on balance.