Skip to content

Is this API binding obsolete? #45

Description

@timcoote

I raised a question with the service support group as some of the responses to this API were becoming slow/incomplete and unpredictable. I was told that I ought to be using v2 of the API and directed to a UI url.

Should this language binding be moving to the v2 'API'?

[nb, in the original terminology of technical architectures, an API is bound to a specific programming language. An interface that's a url is really a protocol, not an API]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions