Update native-api.rst

[BPeuch]

What this PR does / why we need it:
Quotation marks are necessary in this curl command, otherwise bash cannot parse the URLs properly (and the ampersand (&) in the first of the two paths especially confuses it).

Which issue(s) this PR closes:
Closes #6563

[coveralls]

Coverage remained the same at 19.496% when pulling 3835baa on BPeuch:patch-2 into 80c3bbe on IQSS:develop.

[pdurbin]

Looks good (thanks, @BPeuch !). I did also add this commit: c54133c

[pdurbin]

Whoops! I meant to say that I added this commit: 3835baa

Time for coffee. ☕️

[BPeuch]

Thanks, @pdurbin!

[landreev]

What this PR does / why we need it:
Quotation marks are necessary in this curl command, otherwise bash cannot parse the URLs properly (and the ampersand (&) in the first of the two paths especially confuses it).

Which issue(s) this PR closes:
Closes #6563

@BPeuch
@pdurbin
I may be missing something, but this PR still doesn't make much sense to me. You are correct, yes, in that you can't have unquoted ampersands in URLs in shell commands. But in the actual changes you guys committed in this PR, there are NO ampersands in the URLs that you're putting the quotes around.
So no, you DON'T need the double quotes in this example (from the diff):

curl -H "X-Dataverse-key:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -X POST "https://demo.dataverse.org/api/dataverses/root/datasets" --upload-file "dataset-finch1.json"

On the other hand, I'm still seeing some curl examples in that guide with un-quoted URLs that DO have ampersands in them... -?
Like this line, for example - which appears to be the line for which #6563 was originally opened - it looks like it hasn't been fixed:

curl -H X-Dataverse-key:$API_TOKEN -X POST $SERVER_URL/api/dataverses/$DV_ALIAS/datasets/:import?pid=$PERSISTENT_IDENTIFIER&release=yes --upload-file dataset.json

[BPeuch]

Hello, @landreev.

I am responsible for the confusion: I forgot to remove certain local variables from the example before posting it, and there happened to be an ampersand in one of them. I later erased the contents of the variables (it was especially problematic for the admin token) but forgot to update my message elsewhere. Sorry about that.

The general idea still is that certain characters might need escaping and the guidelines should specify that in case they pop up in a query.

[donsizemore]

@landreev @BPeuch the "Datasets" section was next on my list of examples through which to stroll, but there are pending pull requests on the page.

[pdurbin]

Yeah, I also noticed that there are no & but I figured sending the message that it's often good to put URLs in quotes is probably a good thing. I think in the example @BPeuch or his colleague sent me, there were some extra query parameters and hence a & or two.