3 ms·

> It may be better to give each API Key its own default API version, since different applications may expect different versions, and API keys can be a simple wa

> It may be better to give each API Key its own default API version, since different applications may expect different versions, and API keys can be a simple way to differentiate applications That would not work if I (leipert) build a client against version 2022-11-28 and you (rattray) create an API token to use with that client on a later date though, right?

frosted-flakes 4y ago
You can manually set the API version associated with the token.
- rattray 4y ago
  Correct – and when creating the API Key, you'd want the API to give helpful hints about what other parts of the application use (which is trickier than it sounds).
  - leipert 4y ago
    Ah. That makes sense. Similar to choosing scopes then.
easton 4y ago
It works for stripe because it’s one account per company, for GitHub you’d probably set it at the organization level, which would be a bit confusing for personal accounts as you say. I think you could still do it for personal accounts if you allow some kind of override.