Make available API endpoints configurable #113

Open
opened 2023-03-16 20:40:06 +08:00 by johannesmoos · 3 comments
johannesmoos commented 2023-03-16 20:40:06 +08:00 (Migrated from github.com)

Can we make the various API endpoints configurable (on/off)? One might not want to offer all endpoints or the API at all.

Can we make the various API endpoints configurable (on/off)? One might not want to offer all endpoints or the API at all.
annikahannig commented 2023-03-16 21:36:50 +08:00 (Migrated from github.com)

Do you have a specific one in mind? So far the frontend uses all endpoints.

Do you have a specific one in mind? So far the frontend uses all endpoints.
annikahannig commented 2023-03-16 21:53:53 +08:00 (Migrated from github.com)

Some ideas:

  • Resilliance against crawling using ratelimiting
Some ideas: - Resilliance against crawling using ratelimiting
johannesmoos commented 2024-01-30 23:43:47 +08:00 (Migrated from github.com)

Hi @annikahannig, as discussed, /routes is a legacy endpoint and will be removed with the next release (I had this one in mind specifically). Also, I was under the naive impression that the endpoints are decoupled from the UI, i.e. that we can control what endpoints are available via API without breaking the UI/frontend without a huge change.

Hi @annikahannig, as discussed, `/routes` is a legacy endpoint and will be removed with the next release (I had this one in mind specifically). Also, I was under the naive impression that the endpoints are decoupled from the UI, i.e. that we can control what endpoints are available via API without breaking the UI/frontend without a huge change.
Sign in to join this conversation.
No description provided.