I teach young interaction designers how to build things using web APIs. Many others also try to use web APIs to teach kids or adults.

It's now a lot harder than a few years ago.

That's because there's very few unauthenticated endpoints left[1], and when authenticated there's no API mode suitable for teaching the API to a class or workshop group.

I totally understand the need for control and limitations in web APIs.

I'm just asking: would you, web APIs maintainers, be open to have a workshop mode to help teach your APIs without compromising security and ressources ?

As an example: Instagram was easy to use in a learning environment, one of the nicest API to teach a workshop: rich data, accessible, easily working client side in the browser and… cool for students ;-)

With recent restrictions to public content in sandbox mode, it's now very hard:

- Sandbox mode is inadequate for a class (very restricted in term of public content, 10 users). It's restricted in a way that students can't build engaging demos. For example, most of my students don't publish images they have empty accounts, and the sandbox restrict data to their own accounts.

- The Instagram App submission process doesn't account for workshops and learning environnement. (Which makes sense!)

There's similar issues with most APIs. (I use to use Twitter, but it became cumbersome for javascript client-side workshops)

Proposal: It would be great to have an intermediary Workshop mode in web APIs, suitable for teaching and using the API in a workshop context.

As a starting point, it could

- allow access to public content, because it's the easiest way for students to dive in an API.

- use an expiring shared token as auth (given by the teacher) so students don't have to authenticate for most contents.

Would you pledge to implement such a workshop mode? :-)

[1] https://shkspr.mobi/blog/2016/05/easy-apis-without-authentication/