Hi @brandon42,
When you use that API endpoint to create a token on a user's behalf, that user must activate it themselves; I don't have a screenshot handy but when they look at their tokens it will be in the "Pending" state and they will have an "Activate" button they can click. If you hit that POST endpoint for your own user account you should be able to see it. An admin masquerading as the user can explicitly not activate the token and there is no programmatic way to do so, which is a reasonable security consideration on Instructure's part to guarantee that tokens really truly belong to the user they're associated with. If you are trying to make API calls on behalf of other users, the oAuth 2 flow that Chris references is the appropriate way to do so. Lastly, I'm assuming you deleted that token or never activated it, but be careful with your screenshots -- putting that full text token out there could give someone access to your Canvas instance!