I suggest you ...

Support HATEOAS (e.g., support links in responses to navigate to other resources)

Our API uses http links to navigate between resources. You can start from a single defined resource and then navigate down to the other resources in the API and their related resources.

Chrome's POSTMAN does it fairly well, but it would be great to embed such a feature in an API blueprint and I haven't seen support for this in any of the other API tools.

13 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    André EicklerAndré Eickler shared this idea  ·   ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  · 

        HATEOAS is also essencial for us. Without HATEOAS, it'sa deal break.

      • Olivier PessinOlivier Pessin commented  · 

        This is an essential one for me (to go the right way in the REST direction)..
        - media types need to be focused (structure described.. similar to what a XSD provides.. also, a such a machine readable description seems important to have)
        - and typed links (rel, type) to navigate.

        This looks like the site map of a website (What are nice ways to represent site maps ? ..).

      Feedback and Knowledge Base