{
  "id": "p_dqKDSI8GOxeDUxGc",
  "site": "classifieds",
  "url": "https://hagglebee.com/p/p_dqKDSI8GOxeDUxGc",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "Posted by the APIs.io catalog. APIs.io does not own or sell this API; access comes from the provider, Dify.\n\nDify Conversations API covers operations related to managing conversations, with 6 operations drawn from the Dify Service API. It is tagged Conversations and Messaging, and its base URL is https://api.dify.ai/v1. Developers who build chat-style AI applications on Dify would use it to work with the conversations those apps hold with their users.\n\nAbout the provider: Dify is an open-source platform for building AI applications. It combines Backend-as-a-Service and LLMOps, and teams build agentic workflows, chatflows, agents and RAG knowledge pipelines on a visual canvas. Each one can be published as a web app, an embeddable widget, a REST API or an MCP server. Dify is operated by Langgenius, Inc. and comes as Dify Cloud, a self-hosted Community Edition and a commercial Enterprise edition.\n\nPublished for this API: OpenAPI, APIReference and APIsJSON artifacts.\n\nScores for the provider: Kin Score 75.5 (exemplar band) and Agent Readiness 47.5 (agent-ready band), scored 2026-10-31.\n\nAccess: freemium, with self-serve signup and a trial.\n\nPricing: set by the provider.\n\nCondition: a live hosted API listed in the APIs.io catalog.\n\nCatalog listing: https://apis.io/apis/dify/dify-conversations-api/\nProvider: https://dify.ai/",
  "category": "services",
  "location": {
    "city": {
      "geonames_id": 5128581,
      "name": "New York City"
    },
    "country": "US",
    "state": "US-NY"
  },
  "title": "Dify Conversations API – manage chat conversations on Dify's Service API (6 operations)",
  "topics": [
    "conversations-api",
    "llm-apps",
    "messaging"
  ],
  "published_at": "2026-11-01T00:59:07.899Z",
  "expires_at": "2026-12-01T00:59:07.899Z",
  "policy_version": "2026.10.22-1"
}