Skip to content
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

Documenting an API standard #402

Open
3 tasks done
aaronrussellHO opened this issue Apr 9, 2024 · 0 comments · May be fixed by #403
Open
3 tasks done

Documenting an API standard #402

aaronrussellHO opened this issue Apr 9, 2024 · 0 comments · May be fixed by #403

Comments

@aaronrussellHO
Copy link
Contributor

What is the standard you are suggesting?
Documenting an API is an important part of the software design lifecycle. It helps consumers of your API, the wider community and even your own team understand the purpose of endpoints, what and how they work, inputs and outputs etc.

What would be the benefit to the Home Office of adopting this standard?
This would help developers understand how to best help API consumers to use an API. This includes both internal teams as well as wider organisations.

How might people follow it
The documenting standard will overview techniques such as using appropriate methods,

Please confirm the below

  • I have looked at the writing-a-standard standard and think this would meet the standard
  • I have looked through our existing standards and think this is not covered elsewhere
  • I have checked through the open issues on the repository and this standard has not already been suggested
@edhamiltonHO edhamiltonHO linked a pull request May 1, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant