Skip to content

update http mailq api for limit param#831

Merged
dkoerichbird merged 4 commits into
mainfrom
1141-http-mailq-limit
May 22, 2026
Merged

update http mailq api for limit param#831
dkoerichbird merged 4 commits into
mainfrom
1141-http-mailq-limit

Conversation

@juliebin
Copy link
Copy Markdown
Contributor

@juliebin juliebin commented Apr 17, 2026

  • Give your PR a recognizable title. For example: "FE-123: Add new prop to component" or "Resolve Issue Create new-pricing-increases-costs #123: Fix bug in component"
  • Your PR title will be visible in changelogs

What Changed

  • What changes does this PR propose?
  • Provide screenshots or screen recordings for any visual changes.

How To Test or Verify

  • Describe any steps that may help reviewers verify changes.
  • Anything beyond basic unit testing, such as assistive tech usage, or special interactions.

PR Checklist

Below are some checklists to follow for the correct procedure in different circumstance. The first list ("All PRs Checklist") should be followed for ALL PRs. The next 2 are additive to this list depending on what type of PR you are using.

For example: If you are submitting a content change to one of the support documents, your checklist would include the:

  • "All PRs Checklist"
  • AND the "Content Changes Checklist

If you are submitting a feature addition, enhancement, or bug fix, your checklist would include the:

  • "All PRs Checklist"
  • AND the "Development Changes Checklist"

All PRs Checklist

  • Give your pull request a meaningful name.
  • Use lowercase filenames.
  • Apply at least one team label according to which team is the content expert (ie. team-FE or team-SAZ)
  • Pull request approval from the FE team or content experts (see label applied above) that isn't the content creator.

Content Changes Checklist

  • Check that your article looks correct in the preview here or in a Netlify deploy preview.
  • Check the links in your article.
  • Check the images in your article (if there are any)
  • Check to make sure you are using markdown appropriately as outlined in examples/article.md in the root of the project directory and on the momentum doc's preface article
  • Check to make sure the Copy and Tone Guidelines are followed.

Development Changes Checklist (some checks are automatic github actions and will not be listed here. ie. "all tests pass")

  • The appropriate tests are created in cypress/ directory in the root of the project
  • The lighthouse score is passing according to the FE Support Docs' Service Outline SLI/SLOs

Note

Low Risk
Low risk documentation-only change updating the /stats/queues/mailq endpoint docs and adding a related changelog entry; no product code or runtime behavior is modified.

Overview
Updates the /stats/queues/mailq documentation to describe supported query parameters, including a new limit option (default 20), plus clarifies domain/binding filtering and adds ip as an alias for SparkPost-style bindings, with updated examples.

Adds a Momentum 5.3.0 changelog entry (I-1141) noting the new optional limit query parameter.

Reviewed by Cursor Bugbot for commit d7e7457. Bugbot is set up for automated code reviews on this repo. Configure here.

@juliebin juliebin requested a review from Copilot April 17, 2026 14:33
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 17, 2026

Deploy Preview for support-docs ready!

Name Link
🔨 Latest commit 5043688
🔍 Latest deploy log https://app.netlify.com/projects/support-docs/deploys/69e24ca1418b91000945d5b9
😎 Deploy Preview https://deploy-preview-831--support-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Momentum 4 HTTP API documentation for /stats/queues/mailq to reflect support for a limit query parameter (and clarifies related filtering options).

Changes:

  • Updates page metadata (lastUpdated, description) to reflect the revised endpoint behavior.
  • Adds limit (plus ip as an alternative binding selector) to the documented query parameters, including semantics and operational notes.
  • Expands the synopsis/examples to include requests using limit and combined parameters.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread content/momentum/4/http-api-stats/queues-mailq.md Outdated
Signed-off-by: Doug Koerich <douglas.koerich@bird.com>
@netlify
Copy link
Copy Markdown

netlify Bot commented May 22, 2026

Deploy Preview for support-docs ready!

Name Link
🔨 Latest commit d7e7457
🔍 Latest deploy log https://app.netlify.com/projects/support-docs/deploys/6a10a6929634ac000839029c
😎 Deploy Preview https://deploy-preview-831--support-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@dkoerichbird dkoerichbird merged commit d6c7d5a into main May 22, 2026
4 of 6 checks passed
@dkoerichbird dkoerichbird deleted the 1141-http-mailq-limit branch May 22, 2026 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants