ImportError+cannot+import+name+get+jwt+claims+from+flask+jwt

Not specified by the original author.

ImportError: cannot import name 'getjwtclaims' from 'flaskjwtextended'

TL;DR: flask-jwt-extended 4.0 deleted getjwtclaims. Replace it with get_jwt(), which returns the whole decoded token including your custom claims.

ImportError: cannot import name 'get_jwt_claims' from 'flask_jwt_extended'

The fix

1. Replace the import:

from flask_jwt_extended import get_jwt

2. Replace usage. Old:

claims = get_jwt_claims()
role = claims["role"]

New:

claims = get_jwt()
role = claims["role"]

3. Verify:

python -c "from flask_jwt_extended import get_jwt; print('ok')"

Expected output: ok.

Agent? Search Vectle for more: curl -s 'https://vectle.com/api/v1/search?q=flask_jwt_extended+get_jwt_claims+ImportError'

When this applies

• The import worked on flask-jwt-extended 3.x and broke after upgrading to 4.x.
• Old Flask tutorials and codebases using getjwtclaims.
• pip show flask-jwt-extended reports 4.0+.

When it does NOT apply

• No module named 'flask_jwt_extended', which means it is not installed.
• You are on 3.x and want the new API; upgrade first.

Why this happens

The 4.0 rewrite unified the claims accessors: getjwtclaims (custom claims only) and getjwt (all claims) overlapped, so the maintainers kept getjwt and deleted the other. The migration is mechanical because getjwt's return value is a superset of what getjwt_claims returned.

Compatibility

flask-jwt-extended 4.x removed getjwtclaims. get_jwt exists in 3.24+ and all of 4.x.

flask-jwt-extended 4.0 removed getjwtclaims as part of its API cleanup: custom claims are now read from getjwt(), which returns the full decoded token. The codeforphilly/paws-data-pipeline issue 190 reports exactly this ImportError after upgrading, and the fix is replacing getjwtclaims() calls with getjwt(). Pinning flask-jwt-extended below 4 is only a stopgap.

Not specified by the original author.

ModuleNotFoundError: No module named 'flaskjwtextended'

TL;DR: the distribution is called Flask-JWT-Extended. Run pip install Flask-JWT-Extended and the import works.

ModuleNotFoundError: No module named 'flask_jwt_extended'

The fix

pip install Flask-JWT-Extended

Verify:

python -c "from flask_jwt_extended import JWTManager; print('ok')"

Expected output: ok.

Agent? Search Vectle for more: curl -s 'https://vectle.com/api/v1/search?q=flask_jwt_extended+No+module+named'

When this applies

• Fresh virtualenvs, containers, or CI runners.
• The package is missing from requirements.txt.
• You guessed the pip name from the import name and it failed.

When it does NOT apply

• cannot import name 'get_jwt_claims', which is the 4.0 API removal.
• Import errors after installing; then check the active environment.

Why this happens

PyPI distribution names and Python import names are independent, and Flask extensions are repeat offenders: dashed or CamelCase distribution, snake_case module. The PyPI page lists the exact pip command; guessing from the import fails often enough that this is worth a skill.

Compatibility

Flask-JWT-Extended 4.x with Flask 2.x/3.x. Needs PyJWT, installed automatically.

The module is flask_jwt_extended but the distribution is Flask-JWT-Extended, another instance of the pip-name versus import-name mismatch. The PyPI project page documents the exact install command. Fresh virtualenvs, containers, and CI runners hit this whenever the package is missing from requirements.

Not specified by the original author.

ImportError: cannot import name 'TimedJSONWebSignatureSerializer' from 'itsdangerous'

TL;DR: itsdangerous removed TimedJSONWebSignatureSerializer in version 2.1. Replace it with URLSafeTimedSerializer, which does the same timed signed-token job, or pin itsdangerous<2.1 as a stopgap.

ImportError: cannot import name 'TimedJSONWebSignatureSerializer' from 'itsdangerous'

The fix

1. Replace the import:

from itsdangerous import URLSafeTimedSerializer

2. Replace usage. Old:

s = TimedJSONWebSignatureSerializer("secret")
token [your value] 1})

New:

s = URLSafeTimedSerializer("secret")
token [your value] 1})
data = s.loads(token, max_age=3600)

3. Verify:

python -c "from itsdangerous import URLSafeTimedSerializer; print('ok')"

Expected output: ok.

Agent? Search Vectle for more: curl -s 'https://vectle.com/api/v1/search?q=itsdangerous+TimedJSONWebSignatureSerializer'

When this applies

• The import worked before an itsdangerous or Flask upgrade.
• pip show itsdangerous reports 2.1 or newer.
• Old tutorials or vendored code still reference the JWS serializer names.

When it does NOT apply

• The error is cannot import name 'json' from 'itsdangerous', which is the sibling 2.1 removal with its own fix.
• You actually need JWS/JWT features; then use authlib or PyJWT instead.

Why this happens

The maintainers decided JWS did not belong in itsdangerous and deprecated it in 2.0 with warnings, then deleted it in 2.1. Projects that ignored the deprecation warnings broke on upgrade. URLSafeTimedSerializer is the blessed replacement for timed signed tokens and produces URL-safe strings like the old class did.

Compatibility

itsdangerous 2.1+ removed the class. URLSafeTimedSerializer exists in all 2.x versions.

itsdangerous deprecated its JWS serializers (JSONWebSignatureSerializer and TimedJSONWebSignatureSerializer) in 2.0 and removed them entirely in 2.1, telling users to switch to a dedicated JWT library. The pallets/itsdangerous issue 294 is a report of exactly this ImportError after upgrading to 2.1.0, with the maintainer confirming the removal was intentional, and the infobyte/faraday issue 446 documents a downstream project breaking the same way. The standard fix is URLSafeTimedSerializer, which covers the same signed-timed-token use case.