-
Notifications
You must be signed in to change notification settings - Fork 191
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
REST API #215
Comments
I'd be interested in adding this as a PR if it's justified. How much value would it provide for the community to add to this project vs forking and creating a REST only version? In addition Apple has announced support for this in the "near" future: https://twitter.com/KrauseFx/status/1004450869868298240 This project may fill the gap before Apple's update: https://github.com/Crystalnix/testflight-boarding |
@wcandillon Another potential workaround is submitting the form via a POST request as-is. As evidenced in this commit, boarding does not use CSRF protection. Therefore, your calling method does not need to keep track of state/session. Here's an example:
You will obviously not get a nice JSON response, but you could parse the HTML response body for the string Given the pending release of Apple's new API for App Store Connect, boarding might be due for a refactor since it's pretty standalone. I'll open an issue and see what the other contributors think. |
First things first, thank you for this great package, it is literally a life saver 🙌🏻
I was wondering if it was possible to invoke boarding via a REST API? It seems to be protected via an authenticity token? I have no skills with Ruby on Rails so I'm not sure how it would need to be modified in order to support REST?
Also maybe there is a reason of why it doesn't support REST at the moment?
Again, thank you for this great tool!
The text was updated successfully, but these errors were encountered: