Does the API ever care about usernames?

[narthur]

These are all equivalent:

https://www.beeminder.com/api/v1/users/narthur.json?auth_token=[token]
https://www.beeminder.com/api/v1/users/me.json?auth_token=[token]
https://www.beeminder.com/api/v1/users/aliens.json?auth_token=[token]

They all seem to return the user who owns the token.

As are these:

https://www.beeminder.com/api/v1/users/narthur/goals.json?auth_token=[token]
https://www.beeminder.com/api/v1/users/me/goals.json?auth_token=[token]
https://www.beeminder.com/api/v1/users/aliens/goals.json?auth_token=[token]

They all return the tasks of the user who owns the token.

Are there any endpoints in the API that actually care about what you provide as the username?

I’m curious because I’m building a Beeminder wrapper in Python and I’m wondering if I can skip requiring a username and just rely on the user’s token.

[drtall]

The documentation at Beeminder API Reference says

Since appending an access_token to the request uniquely identifies a user, you can alternatively make the request to /users/me.json (without the username).

[narthur]

@drtall Right, but that’s specific to the users endpoint, so it doesn’t really tell me if that’s the case for the whole API.

Also… even that note isn’t entirely accurate, as it isn’t just “me” you can use. It will accept any string.

[drtall]

Ah fair enough. Sorry I don’t know more than this

[narthur]

No worries.