ADD Doc API keys endpoints to documentation

[hexaltation]

Must be merge at the same time than gristlabs/grist-core#1115
for the new API endpoints can be accessible via console API.

Related to gristlabs/grist-core#579

[netlify]

❌ Deploy Preview for grist-help-preview failed.

Name	Link
🔨 Latest commit	8c1f6c2
🔍 Latest deploy log	https://app.netlify.com/sites/grist-help-preview/deploys/66bb5a802964400008e43e50

[netlify]

❌ Deploy Preview for grist-help-preview failed.

Name	Link
🔨 Latest commit	8c1f6c2
🔍 Latest deploy log	https://app.netlify.com/sites/grist-help-preview/deploys/66bb5a802964400008e43e50

[netlify]

❌ Deploy Preview for grist-help-preview failed.

Name	Link
🔨 Latest commit	8c1f6c2
🔍 Latest deploy log	https://app.netlify.com/sites/grist-help-preview/deploys/66bb5a802964400008e43e50

[fflorent]

Fixes gristlabs/grist-core#579

Wait, will it really fix this issue?
Using this syntax will close as completed the above issue.

[hexaltation]

Fixes gristlabs/grist-core#579

Wait, will it really fix this issue? Using this syntax will close as completed the above issue.

I'm ok that it's not perfect but I want to keep track the fact that this PR needs to be merge at the same time as the functional one.

/api/grist.yml is much code than doc to me, as it's functionally used in production by console api to interact with the app.

Can't it be better to move it to gristlabs/grist-core and to pull it when doc is built ?

@gristlabs people do you have an opinion over this ?

[dsagal]

I agree with @fflorent that the comment on the PR seems risky -- not sure it would actually close the issue in the other repo. Anyway, it would be helpful to have a clearer title and description for the PR, perhaps like "Add OpenAPI spec for the new Doc API keys endpoints in gristlabs/grist-core#579"?

I also agree with @hexaltation suggestion to move /api/grist.yml into grist-core! Good idea! It would make it easier to keep grist.yml up-to-date. It would also help keep the API Console in sync with the current version of Grist.