shopping API uses X-EBAY-API-SITE-ID not X-EBAY-API-SITEID #46
Conversation
This file contains 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
timotheus
added a commit
that referenced
this pull request
Jan 14, 2014
shopping API uses X-EBAY-API-SITE-ID not X-EBAY-API-SITEID
|
Good catch. Thanks Jeff. |
timotheus
added a commit
that referenced
this pull request
Apr 11, 2017
shopping API uses X-EBAY-API-SITE-ID not X-EBAY-API-SITEID
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a fix for the shopping API to use sites other than the default.
There is a similar X-EBAY-API-SITEID on trading and merchandising classes. I don't think merchandising used either spelling of the SITE-ID header as far as I can tell and I ran out of patience with the documentation before I checked on trading. I don't know if others like finding would need something similar.