Build the integration
your workflow needs.

OpenAPI describes the contract.

The public specification describes endpoints, parameters, request and response schemas, and security requirements. YAML and JSON expose the same API contract in two formats.

Use the schema with an API explorer or compatible code-generation tool. Review the generated code and authentication handling before running it. OpenAPI does not automatically connect every AI product or create a ready-made integration.

Authenticate as a Dovod user.

For a personal script, create an API key in Dovod Settings → API Keys and supply it in the Authorization bearer header. Store the key in your environment or secret manager. Team permissions continue to apply.

The specification documents security per operation; public documentation and authenticated project endpoints have different access requirements.

Start by listing your projects.

Set DOVOD_API_KEY in your local environment before running this read-only request. The UI calls them projects; the HTTP resource is named researches.

curl --fail --silent --show-error \
  -H "Authorization: Bearer $DOVOD_API_KEY" \
  https://dovod.app/api/researches

A successful response contains the researches your user can access. A new account may return an empty collection. Run the request in your own environment after setting the credential.

Keep the API contract and workflow together.

Use the OpenAPI schema for exact payloads and errors. Use the Domain Guide for relationships and the Conducting Research guide for the sequence of work. MCP tools and HTTP routes serve different clients; do not assume every HTTP action is also an MCP tool.