Skip to content

[DOCS]: Correct _cat/count method to GET#6013

Merged
charlotte-hoblik merged 2 commits intomainfrom
charlotte-get-post-4598
Feb 12, 2026
Merged

[DOCS]: Correct _cat/count method to GET#6013
charlotte-hoblik merged 2 commits intomainfrom
charlotte-get-post-4598

Conversation

@charlotte-hoblik
Copy link
Contributor

@charlotte-hoblik charlotte-hoblik commented Feb 11, 2026

Updates the documentation to correctly list the _cat/count endpoint as a GET request instead of POST.

Connected to: elastic/docs-content#4598

Preview:
Screenshot 2026-02-11 at 17 36 15

@github-actions
Copy link
Contributor

Following you can find the validation changes against the target branch for the APIs.

No changes detected.

You can validate these APIs yourself by using the make validate target.

@pquentin
Copy link
Member

This isn't a mistake, _cat/count also supports POST since Elasticsearch 9.3.0: elastic/elasticsearch#138369. I don't know if there's a way to specify that in the docs, though.

@charlotte-hoblik
Copy link
Contributor Author

Thanks @pquentin! To clarify, I didn't remove POST, I just swapped the order so the UI defaults to GET (since that's the main use case). Good call on the 9.3 update though. I'll add a note to the description clarifying that POST is supported for serverless routing.

Copy link

@KyleOnK8s KyleOnK8s left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Member

@pquentin pquentin left a comment

Choose a reason for hiding this comment

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

Thanks! LGTM.

I've removed the 9.1 backport, as there isn't any new 9.1 release planned.

@charlotte-hoblik charlotte-hoblik merged commit f2e86a6 into main Feb 12, 2026
12 checks passed
@charlotte-hoblik charlotte-hoblik deleted the charlotte-get-post-4598 branch February 12, 2026 08:53
@github-actions
Copy link
Contributor

The backport to 9.2 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-9.2 9.2
# Navigate to the new working tree
cd .worktrees/backport-9.2
# Create a new branch
git switch --create backport-6013-to-9.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f2e86a6bbc03b1e2732d163cf6ca3e07ba578ac1
# Push it to GitHub
git push --set-upstream origin backport-6013-to-9.2
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.2

Then, create a pull request where the base branch is 9.2 and the compare/head branch is backport-6013-to-9.2.

@github-actions
Copy link
Contributor

The backport to 9.3 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-9.3 9.3
# Navigate to the new working tree
cd .worktrees/backport-9.3
# Create a new branch
git switch --create backport-6013-to-9.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f2e86a6bbc03b1e2732d163cf6ca3e07ba578ac1
# Push it to GitHub
git push --set-upstream origin backport-6013-to-9.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.3

Then, create a pull request where the base branch is 9.3 and the compare/head branch is backport-6013-to-9.3.

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

Comments