Document usage limits policy reset fields in OpenAPI spec - #546
Closed
itsthusharashenoi wants to merge 338 commits into
Closed
Document usage limits policy reset fields in OpenAPI spec#546itsthusharashenoi wants to merge 338 commits into
itsthusharashenoi wants to merge 338 commits into
Conversation
overhaul auth schema for inference APIs
feat: custom logger endpoint
Revert "feat: custom logger endpoint"
…m_log feat: custom logger endpoint
Update branch
Code snippets
more code samples
Update Virtual Key response structure
Prompts Render API
add parameters & fine-tuning description update
feat: SDK example for log export endpoints
fix: add azure config spec
…ge-apis Chore/add mcp connection manage apis
chore: add custom_host support integration models
feat: add api key rotation policy and update
…nges feat: scim group mappings endpoints definitions
Adds the optional pricing_adjustments field to CreateIntegrationRequest, UpdateIntegrationRequest, and IntegrationDetailResponse, plus the new PricingAdjustments and PricingMultiplier component schemas. The multiplier keys mirror the pricing keys in the Portkey Models database.
Add pricing_adjustments to integrations API
- Added support for secret mappings in MCP integration requests and responses, allowing dynamic resolution of secrets from secret references. - Introduced a new value_format field to specify the format of secret values (string or json) for better handling of structured objects.
…rmat-mcp Enhance OpenAPI schema for MCP integrations
feat: add default config slug in workspace
Add periodic_reset_days, next_usage_reset_at, and last_reset_at to UsageLimitsPolicy so list and get responses match the documented schema. Co-authored-by: Cursor <cursoragent@cursor.com>
patrickdavidryan6-sys
approved these changes
Jul 8, 2026
Contributor
|
Looks like this PR took a wrong turn at the fork 🍴 and wandered upstream. The intended Portkey change landed in Portkey-AI#144, while this branch brings the whole Portkey spec along for the ride. Closing this accidental detour—safe travels! 🚂 |
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
17 participants
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.
Updates the OpenAPI spec to match what the usage limits list and get APIs already return.
Related backend fix: albus#2165 — list now returns the same policy fields as get (including periodic_reset, credit_limit, conditions, etc.) by passing optional select in the list controller.
What changed
Added three missing fields to UsageLimitsPolicy in openapi.yaml:
List and get both use this schema, but these reset-related fields were returned by the API and not documented.
Why
Customers and internal docs should reflect the real API response. The albus PR fixes list behavior; this PR keeps the public spec in sync for the reset fields that were missing.