Conversation
AmirPracti
approved these changes
Jun 9, 2026
…ies and JDK 23" This reverts commit 05a4b91.
|
🥷 Code experts: deshilovPT, stask shmuelko, deshilovPT have most 🧠 knowledge in the files. See details
Knowledge based on git-blame:
Knowledge based on git-blame:
Knowledge based on git-blame:
Knowledge based on git-blame:
Knowledge based on git-blame:
Knowledge based on git-blame: ✨ Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes https://practitest-uri.atlassian.net/browse/PT1-7467, https://practitest-uri.atlassian.net/browse/PT1-7428, https://practitest-uri.atlassian.net/browse/PT1-2640
Description
What has been changed?
Added a new
GET /api/v2/accountendpoint that returns account-level information, currentlyexposing the API rate limit (
api_max).Why is this needed?
API consumers need a way to programmatically retrieve account-level settings — specifically the
effective API rate limit — so they can self-throttle and avoid hitting 429 errors.
Implementation Details
Api::V2::AccountsController#show— renders the account using the standardJSON:API envelope via
BaseApiControllerAccountSerializer— exposesidandapi_maxattributesresource :account, only: [:show]added underapi/v2namespaceapi_max_periodremoved from account serializer (not needed for this endpoint)Automation:
spec/controllers/api/v2/accounts_controller_spec.rb—covers 200 response, default and custom rate limits)
Additional Notes
The endpoint is account-scoped (authenticated via account token, same as other v2 endpoints). No new
external dependencies.