-
Notifications
You must be signed in to change notification settings - Fork 615
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
Calls fail if api methods have periods in them #1
Comments
thanks for filing an issue. i just published a fix for your problem (version 0.5.2). you can verify the mapping via: |
looking at the wsdl (and the mapping) again, it seems like the period-separated "namespaces" in front of the actual soap actions may not affect Savon. "User.GetApiKey" might be dispatched via:
but of course i would need to test this with a similar api to make sure it actually works. would love to get some feedback on this one. |
You can still dispatch the command but it errors trying to get the result because the soap action is sent as GetApiKey instead of User.GetApiKey. I think the namespaces would have to be appended in some manner to the call for this to work correctly. I will try it with 0.5.2 |
re-opened. investigating ... |
i just release version 0.6.0 which should fix your problem. I had to make quite a few changes to the API in order to gain flexibility, so please read the Wiki before using the new version. You should be able to (for example) retrieve your API key via:
Please let me know if this works for you |
Hey, I was trying to test this out with the CampaignMonitor API. Unfortunately the api uses a format where the soap command contain periods (User.GetClients, Campaign.GetLists) etc.
Is there any way to get around this? Otherwise, very cool library.
The text was updated successfully, but these errors were encountered: