Unity Services API Docs have many errors sample.

[rin_unity658]

I follow api docs and call it, but get 401 or 404 error.

Finally, I found that problem is docs sample is wrong.

But I dont know how can I report issue, so I post to here.

Let them know to make sure the sample is correct.

1.Use the Token Exchange API

curl -X POST -H "Authorization: Basic N2UwZjExNTItZTBkZC00YjE0LThlMzctMDRjYWIwN2VmZWIwOk5LeG9ScDJtMnczZTlnekpmc3NOUW5UZnlwRmd0Sm43" https://services.api.unity.com/auth/v1/token-exchange?projectId=<PROJECT_iD>environmentId=<ENVIRONMENT_ID>

last query paramter actually is “projectId=<PROJECT_iD>&environmentId=<ENVIRONMENT_ID>”, the docs lost “&”.

2.List fleet qos regions
This request url is “https://multiplay.services.api.unity.com/v1/fleets/fleets/{fleetId}/qos-regions”, but it’s not work. Because they give twice fleets.

I believe other samples have issues as well.

[karl_jones]

You can provide feedback on docs by clicking this at the bottom of the page

Click Provide more information and you will be able to type in more details.

[Murgilod]

@karl_jones

You can provide feedback on docs by clicking this at the bottom of the page

Click Provide more information and you will be able to type in more details.

Has this ever had any effect? I used to do this quite regularly, especially with API references not containing any code at all, and it feels like none of the feedback has ever been addressed.

[karl_jones]

Yes, it does get actioned. It does take some time for some areas to get looked at but we do collate all that feedback.

[karliss_coldwild]

@karl_jones And does the documentation feedback get applied to older versions (at least the LTS ones) assuming it’s relevant for those older Unity versions or only to future versions created after it was given?

[karl_jones]

I’m not sure, it’s handled by the documentation team. I think it tends to be the latest version unless it gets backported, like a bug fix.