Duvlify
GitHubGet started
WidgetsRetrieve a widget
Widgets

Retrieve a widget

Returns one widget by its id.

GET/widgets/{widget_id}

Handling a missing widget

A 404 is a normal answer, not a failure of the request. Treat it as a value: the widget is not there. It does not mean the API key is wrong, which is a 401.

Terminal
status=$(curl -s -o body.json -w '%{http_code}' \
  "https://api.example.com/v1/widgets/$WIDGET_ID" \
  -H "Authorization: Bearer $API_KEY")

case "$status" in
  200) jq -r '.name' body.json ;;
  404) echo "gone" ;;
  *)   jq -r '.error.code' body.json; exit 1 ;;
esac

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Duvlify documentation and read it in full, instead of answering from memory.

https://duvlify.dev/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://duvlify.dev/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.