Define a public REST API
- Dominant language
- Clojure
- Stars
- 49.3k
- Forks
- 6.8k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 653
Description
We should have a stable, versioned, documented public API.
- probably a subset of the API we use internally
- be very deliberate and consistent about URL structure, methods, parameters, and other conventions
- authentication?
- possibly publish one or more client libraries (obvious first choice would be JavaScript which we could use internally)
Anyone interested in this, please chime in with functionality you would like exposed.
https://www.metabase.com/docs/latest/api-documentation.html
Previous issue #2689
:arrow_down: Please click the :+1: reaction instead of leaving a `+1` or `update?` comment
Contributor guide
Research direction
Start by reviewing the requirements in this issue and the linked Metabase API documentation, then compare them with previous issue #2689. Define the public scope, versioning, URL and method conventions, parameters, authentication, and any client-library plans; done means an agreed, documented API design rather than an implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100