This repository contains OpenAPI models for developers to use when developing software to call Selling Partner APIs.
C-Rank Grade: D (Risky) - 26/100
External PR Merge Rate: -
Response Time: 3d
First Timer Success: -
amzn/selling-partner-api-models has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in amzn/selling-partner-api-models respond to incoming external pull requests in approximately 78.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 26.0 places amzn/selling-partner-api-models in the D tier.
The external contributor pull request merge rate for amzn/selling-partner-api-models is 0.0%, based on public PR activity from non-core contributors.
amzn/selling-partner-api-models currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
This repository contains OpenAPI models for developers to use when developing software to call Selling Partner APIs.
Strict review standards in amzn/selling-partner-api-models. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in amzn/selling-partner-api-models focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/amzn/selling-partner-api-models?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~51 hours (81% approval). Large PRs (>500 lines) take ~379 hours (29% approval). Keep your diff compact for rapid review.
The anonymized buyer email ([email protected]) was previously returned by default in the Orders API v0 getOrders and getOrder responses without requiring a Restricted Data Token (RDT) or any restricted roles. This field has been silently removed from the response with no deprecation notice or entry in the SP-API Release Notes. What changed Before: BuyerEmail (e.g. [email protected]) was returned in every order response — both FBA and FBM — without RDT and without any restricted roles. Now: The field is no longer returned in either the v0 or v2026-01-01 API, regardless of whether includedData=BUYER is specified. Why this is a problem No deprecation notice. The SP-API Release Notes contain no mention of this change. The field was removed without any advance warning. Not actual PII. The buyerEmail field is Amazon's own anonymized relay address (@marketplace.amazon.com), not the customer's real email. It cannot be used to identify the buyer. Gating
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to amzn/selling-partner-api-models, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of amzn/selling-partner-api-models acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
amzn/selling-partner-api-models has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 26.0 places amzn/selling-partner-api-models in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, amzn/selling-partner-api-models currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for amzn/selling-partner-api-models are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.