API-Endpunkte
We also recognize that not all companies provide standardized APIs, so we built an in-house widget to let you describe to your team or customers what your API looks like.
Additionally, it's super useful when working together with external teams, where you need to communicate an API specification, and instead of providing a JSON file, you provide a document with this widget, and let it describe anything from URL, Parameters, Cookies, Request structure, Response structure, etc.
You can add one by typing (api) in the editor or clicking the API icon in a new row.
fetch("https://api.cakes.com/v1/cakes/:id", {
"method": "POST",
"headers": {
"Accept": "application/json"
}
})
.then(response => {
console.log(response);
})
.catch(err => {
console.error(err);
});fetch("https://api.cakes.com", {
"method": "GET",
"headers": {
"Accept": "application/json"
}
})
.then(response => {
console.log(response);
})
.catch(err => {
console.error(err);
});It's VERY flexible letting your team describe in detail any type of HTTP endpoint.
We're also working on making it interactive, so your customers can actually make the request from here.
Andere Blöcke finden
Discover new ways and blocks to create stunning and functional documentation pages.
Brauchen Sie Hilfe? ⬇️
Use the blau Sprechblase from bottom right corner.
Or try KI-Chat (from search box) for quick answers.
Ihre Meinung ist wichtig
Use the below feedback form, anonymously.
Or ask a question in Frage-und-Antworten-Bereich and our team or AI will give you a solution.