-
Notifications
You must be signed in to change notification settings - Fork 3k
Added postman collection for backend API #3726
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
base: develop
Are you sure you want to change the base?
Conversation
Hey there, I was able to import this collection into Postman (in a bit of a roundabout way) and tried to create a host, but it appears the payload sent in the body doesn't match what is sent when it's done via the GUI. Body payload in the collection:
Working payload taken from the request in the GUI (and reproduced in Postman); this was using a cert created from Cloudflare, rather than Let's Encrypt:
Using the original payload returns a 400 "internal error" (which is not terribly useful in troubleshooting :) ) Doing some quick testing and trying to match the 1st to 2nd body, I think I discovered the error: "enables" should be "enabled". Even matching the body almost exactly would then return a "400 data should NOT have additional properties" error: Changed the s to a and it worked! Also need to mention that the domain_names field requires "" around the subdomain, otherwise the same Internal Server Error error is returned: "domain_names": ["subdomain.domain.com"] |
On the |
CI Error:
|
PR is now considered stale. If you want to keep it open, please comment 👍 |
No description provided.