What am I doing wrong?

[quackduck]

$ xurl auth oauth1 --consumer-key IiXX...iaYNBP --consumer-secret Rvl9RQl...VJnayU --access-token 106560...u975UixF3YUO7b --token-secret eFVeG...whV5k9jDXX
OAuth1 credentials saved successfully!
$ xurl auth status
OAuth2 Accounts:
OAuth1: Configured
$ xurl --auth oauth1 /2/tweets
{
  "detail": "Unauthorized",
  "status": 401,
  "title": "Unauthorized",
  "type": "about:blank"
}

[santiagomed]

Can you try /2/tweets/:id ?

[quackduck]

same thing

$ xurl --auth oauth1 /2/tweets/:id
{
  "detail": "Unauthorized",
  "status": 401,
  "title": "Unauthorized",
  "type": "about:blank"
}

[quackduck]

I just regenned and tried adding in my keys and secrets again. No change. Something I'm confused about: at no point have I had to enter the Bearer Token. Is this expected?

[santiagomed]

You want an actual post id instead of :id. For example /2/tweets/20

[quackduck]

Same thing

xurl --auth oauth1 /2/tweets/20
{
  "detail": "Unauthorized",
  "status": 401,
  "title": "Unauthorized",
  "type": "about:blank"
}

[santiagomed]

Oh I think you are right, /2/tweets/:id only support App-only auth which is through the bearer token. App auth support will be included in the next release.

[quackduck]

ah okay when can i expect that? also what's a good endpoint to test out user point of view api access? thanks for your help!

[santiagomed]

The release is live! You can update xurl by running the install command again

also what's a good endpoint to test out user point of view api access?

what do you mean? timelines?