Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Make endpoints in API responses full URLs #142

@techgique

Description

@techgique

The endpoint(s) keys have values which are relative URLs from the app root. This means to browse between them in the browser, one has to type them in. Full URLs are clickable and make browsing much easier.

https://cdrhapi.unl.edu/v2/

endpoints:
0 | "/"
1 | "/items"
2 | "/item/{id}"
3 | "/collections"
4 | "/collection/{collection}/info"
5 | "/collection/{collection}/item/{id}"

The template URLs obviously can't be made into full URLs, but making the others clickable would make browsing to them much easier. The template URLs would be full URLs at the parent endpoints such as https://cdrhapi.unl.edu/v2/collections

endpoint | "/v2/collection/habeascorpus"

The Chronicling America API and recent reintroduction as the Open ONI Chronam API highlighted how much more convenient browsing an API in the browser can be with full URLs:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions