Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fps.connection.get_token_by_caller_reference returns 400 Bad Request for valid caller reference #323

Closed
johnpena opened this issue Sep 7, 2011 · 0 comments
Closed

fps.connection.get_token_by_caller_reference returns 400 Bad Request for valid caller reference #323

johnpena opened this issue Sep 7, 2011 · 0 comments
Assignees
@garnaat
Labels
bug fps
Milestone
2.1.0

Comments

@johnpena
Copy link

johnpena commented Sep 7, 2011

I'm trying to reissue a payment that was marked as pending. I have a caller_reference and a transaction_id stored in my database, and have verified that both are correct by checking the transaction details in my amazon account.

When I try to get the token using connection.get_token_by_caller_reference(my_caller_reference), the following error is raised:

FPSResponseError: FPSResponseError: 400 Bad Request

InvalidRequestThe request doesn't conform to the interface specification in the WSDL. Element/Parameter ":callerReference" in request is either invalid or is found at unexpected location ...

What is causing this to arise? Shouldn't this work fine if the caller reference is valid?
@ghost ghost assigned garnaat Oct 25, 2011
msabramo pushed a commit to msabramo/boto that referenced this issue Nov 28, 2012
@garnaat
Fixed name of CallerReference parameter in get_token_by_caller_refere…
6d3830a 
…nce method. Closes boto#323.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@garnaat garnaat

Labels
bug fps
Projects
None yet
Milestone
2.1.0
Development

No branches or pull requests
2 participants
@garnaat @johnpena