Skip to content
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.

Post variables as FORM-DATA? #424

Closed
fh-thudson opened this issue Mar 13, 2018 · 3 comments
Closed

Post variables as FORM-DATA? #424

fh-thudson opened this issue Mar 13, 2018 · 3 comments

Comments

@fh-thudson
Copy link

Hey guys,

I love apiary it looks 100 times better than swagger. The only issue that I am having is I just post form data on endpoints. I can't seem to understand how to tell apiary that it's not a JSON in the body of the post. I would love for the attributes to come up just as it would for URI parameters. I like how that looks. I don't want just an empty body section on the endpoint because let's face it users aren't very intelligent. If I can't do this I can just use swagger still and that works just fine.

Please and thank you for any help I can receive.

image

@fh-thudson
Copy link
Author

It was a lug nut... Fixed it!

image

@fh-thudson
Copy link
Author

Is there any way I can get that Authorization "Token" to be dynamic and stored from the 1st authorization endpoint?

@kylef
Copy link
Member

kylef commented Jan 10, 2019

Hi @fh-thudson, we do plan to bring MSON to both headers and parameters (currently tracked in apiaryio/api-blueprint-rfcs#3).

As for the question regarding storing an authorization token. Headers in API Blueprint are purely example, the values are not fixed. As for storing headers between requests it sounds like a feature request for any tooling you are using. For example, the Apiary console allows you to mark a header as persistent and then it will be applied to every request made via the console (https://help.apiary.io/tools/interactive-documentation/#persistent-http-headers-in-console).

Does that answer your questions?

@kylef kylef closed this as completed Jan 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants