feat: Add extra_headers argument to allow setting additional user headers
#601
+130
−2
Conversation
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
janbuchar
approved these changes
Feb 2, 2026
Contributor
janbuchar
left a comment
janbuchar
left a comment
There was a problem hiding this comment.
LGTM code-wise, but I can't help but ask, what is the actual problem that this is solving? I went through the linked issue, but I still don't understand why people need to access the Apify API with custom headers. Bear in mind this is just my desire to learn, not being annoying.
Collaborator
Author
I can imagine a working environment where traffic to all external services is proxied, and headers serve as authentication to the proxy.
Wasn't thinking that until you mentioned it 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
This PR adds the
extra_headersargument forApifyClientandApifyClientAsync, which allows you to set additional custom headers in the HTTP client. The set headers will be applied to all requests. Custom headers cannot override default headers set in the client.This solves the problem case described in #416 (comment)
Testing
Tests checking the set headers have been added.