Skip to content

GRAL-6060 document signed token caching behavior #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pipedrive-public-gha-bot merged 6 commits into from
Aug 25, 2026
Merged

GRAL-6060 document signed token caching behavior #73

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
d804591
GRAL-6060 document signed token caching behavior
dmitriyeff Aug 25, 2026
131310a
GRAL-6060-readme-update undo types install
dmitriyeff Aug 25, 2026
3754216
GRAL-6060-readme-update re-create package-lock
dmitriyeff Aug 25, 2026
9c3db93
GRAL-6060-readme-update revert package-lock
dmitriyeff Aug 25, 2026
2643976
GRAL-6060-readme-update changelog update
dmitriyeff Aug 25, 2026
e78252a
GRAL-6060-readme-update resolve conflicts
dmitriyeff Aug 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.

## [Unreleased]

### Changed
- Document `GET_SIGNED_TOKEN` cached token behavior in README

## [0.16.0] - 2026-05-22

## [0.15.1] - 2026-04-28
Expand Down
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -212,6 +212,10 @@ JWT can be used to ensure that the custom UI extension is loaded by Pipedrive. I
requests and be verified on the server side. As JWT expires in 5 minutes, you can use this command
to get a new one.

If the previously issued token for the extension hasn't expired yet, calling this command again
returns that same cached token instead of generating a new one. This means calling it repeatedly
in a short time span is safe and won't produce a different token each time.

**Response**

| Parameter | Type | Description | Notes |
Expand Down
Loading