Closed marcogruhl closed 1 year ago
Hmm, I'm not sure about this unfortunately (and I need to archive this repository as it is not something I'm doing any active work on).
Are you able to call the API via any other means e.g. using Postman or twurl - does your application and project have permission to call the endpoints / functions you are trying to use? if you're trying to access the v1.1 streaming API for example, you can't do that any more.
A couple of other small things to check:
Apart from that I'd have to suggest the Twitter developer forums for assistance.
I'm going to close this since it is not an issue with this project itself.
Thank you for your answer and sorry for the inconvenience. For completion: I can access all "App-Endpoints" with the bearer token. I just call v2 endpoints. Time and Windows version are up to date. I will investigate further by my self. PS: do you still have access to the twitter API and does this program still run? If yes, i can use it as "reference" and try to fix my token problems. Tank you anyway, marco
Hello Andy,
i think this is not a real issue on your side, but maybe you can help me or have just some advice.
I came across your repo while trying to implement the user scope for the TwitterSharp API. I also recognized that you starred this repository.
I generated the 4 tokens ( consumer-key, consumer-secret, access-token, access-secret) from the twitter developer portal. I also regenerated them completely but always get unauthorized. The authorization header looks good (at least to me) What could i have done wrong?
thanks in advance, marco