Move "Refetch host by token" to public API#40017
Open
noahtalerman wants to merge 5 commits intomainfrom
Open
Conversation
- Users/customers use it:
fleet-release
previously approved these changes
Feb 18, 2026
noahtalerman
had a problem deploying
to
Docker Hub
GitHub Actions
Error
fleet-release
approved these changes
Feb 18, 2026
noahtalerman
temporarily deployed
to
Docker Hub
GitHub Actions
Inactive
noahtalerman
changed the title
fleet-release
approved these changes
Feb 18, 2026
fleet-release
approved these changes
Feb 18, 2026
fleet-release
previously approved these changes
Feb 18, 2026
noahtalerman
commented
Feb 18, 2026
Comment on lines
-3183
to
-3190
| #### Request headers | ||
|
|
||
| This endpoint accepts the `X-Client-Cert-Serial` header for authentication in addition to device token authentication. | ||
|
|
||
| The `Authorization` header must be formatted as follows: | ||
|
|
||
| ``` | ||
| X-Client-Cert-Serial: <fleet_identity_scep_cert_serial> |
Member
Author
There was a problem hiding this comment.
@marko-lisica this isn't relevant anymore right? IIRC we were going to use this when we required a SCEP cert for the iOS/iPadOS My device page. I think that's not the case anymore.
rachaelshaw
requested changes
Feb 20, 2026
docs/REST API/rest-api.md
Outdated
| Flags the host details, labels and policies to be refetched the next time the host checks in for distributed queries. Note that we cannot be certain when the host will actually check in and update the query results. Further requests to the host APIs will indicate that the refetch has been requested through the `refetch_requested` field on the host object. | ||
|
|
||
| `POST /api/v1/fleet/hosts/:id/refetch` | ||
| `POST /api/v1/fleet/hosts/:id/refetch` or `POST /api/v1/fleet/device/:token/refetch` |
Member
There was a problem hiding this comment.
@noahtalerman these are still separate endpoints, right? Even though it's duplicative, I think we should document these separately. (Maybe "Refetch host" and "Refetch host by Fleet Desktop token"?) It'd be easier to parse as a reader of the docs (likely to be referencing a single endpoint at a time). Less cognitive load to focus on 1 endpoint URL with 1 required parameter, versus 2 URLs and 2 parameters that may or may not be required depending on which URL you use.
Member
Author
There was a problem hiding this comment.
Makes sense! I broke them out.
noahtalerman
pushed a commit
that referenced
this pull request
Feb 20, 2026
To be consistent with naming in @noahtalerman's PR: #40017
fleet-release
previously approved these changes
Feb 20, 2026
noahtalerman
had a problem deploying
to
Docker Hub
GitHub Actions
Error
noahtalerman
commented
Feb 20, 2026
fleet-release
previously approved these changes
Feb 20, 2026
noahtalerman
had a problem deploying
to
Docker Hub
GitHub Actions
Error
fleet-release
approved these changes
Feb 20, 2026
noahtalerman
temporarily deployed
to
Docker Hub
GitHub Actions
Inactive
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
3 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.
Uh oh!
There was an error while loading. Please reload this page.