5
403 on API endpoints (lemmy.readme.io)
submitted 2 years ago by to c/meta@programming.dev
6 comments fedilink hide all child comments
 

Tried to use several different API endpoints as described in the link, but they all return 403 with a cloudflare "Just a moment..." html reply. Even tried copying an existing jwt token from a working logged-in browser but the same thing still happens.

Any idea what I could be doing wrong?

curl -v --request POST \
     --url https://programming.dev/api/v3/user/login \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '{"username_or_email": "redacted", "password": "redacted"}'
...
< HTTP/2 403
...

<!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title>
...

all 6 comments

sorted by: hot top controversial new old
[–] 5 points 2 years ago (1 child)

You're not passing cloudflares anti bot challenge. This is known to be a hard problem, as obviously CF is highly motivated to stop bots

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    • [–] 3 points 2 years ago*

    If you want to run a bot against our api I'm able to whitelist ips to bypass the bot check. Feel free to reach out on matrix

  • permalink
  • fedilink
  • source
    •
    [–] 3 points 2 years ago (1 child)

    I have no knowledge of this specific issue but 403 means unauthorized and the "Just a moment" response is usually because the server sends a JavaScript challenge to verify that you are a 'real' browser/user. It's an anti bot verification and you're not passing.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •