Skip to content

Should the API be able to self-describe the available services ? #13

@pierrecamilleri

Description

@pierrecamilleri

Some features of the proposed API are optional for the MSP to implement (e.g. booking without deep link).

What do you think of implementing a specific endpoint so that the MaaS can fetch the information of what services are available ?
Directly inspired by TOMP APIs /operator/meta endpoint, where they also give additional information such as the version of the standard used and so on.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions