Productboard API
connection[issueKey] query parameter removal on GET /v2/jira-integrations/{id}/connections
Stopped workingSubscribe to Productboard APIShare
Calls to GET /v2/jira-integrations/{id}/connections, query parameter connection[issueKey] on Productboard API stopped working on April 2, 2026.
Calls it hits
GET /v2/jira-integrations/{id}/connectionsquery parameter connection[issueKey]
What to use instead of these calls
Send issueKey instead of connection[issueKey].
In Productboard API's words
connection[issueKey] → issueKey
Facts
- API
- Productboard API
api.productboard.com - Kind
- Parameter removal
- Announced
- April 2, 2026
- Takes effect
- April 2, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Productboard API's own pages
Questions
When does this change take effect?
Calls to GET /v2/jira-integrations/{id}/connections, query parameter connection[issueKey] on Productboard API stopped working on April 2, 2026.
What happens to calls after April 2, 2026?
They have failed since April 2, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Productboard API 10
-
GET /v2/jira-integrations/{id}/connectionsParameter removal Stopped working -
POST /v2/notes/searchParameter removal Stopped working -
POST /v2/notes/searchParameter removal Stopped working -
POST /v2/notes/searchParameter removal Stopped working -
POST /v2/members/searchParameter removal Stopped working -
POST /v2/teams/searchParameter removal Stopped working -
POST /v2/members/searchParameter removal Stopped working -
POST /v2/notes/searchParameter removal Stopped working -
POST /v2/teams/searchParameter removal Stopped working -
POST /v2/members/searchParameter removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.