[{"data":1,"prerenderedAt":137},["ShallowReactive",2],{"blog-en-1tool-api-documentation-openapi-live":3},{"id":4,"title":5,"body":6,"categories":117,"date":119,"description":12,"draft":120,"excerpt":121,"extension":122,"image":123,"lang":124,"meta":125,"modified":126,"navigation":127,"noindex":120,"path":128,"related":121,"seo":129,"seoDescription":130,"seoTitle":131,"slug":132,"sourcePath":133,"sourceRoute":121,"stem":134,"tags":121,"translated":120,"type":135,"wpId":121,"__hash__":136},"blog\u002Fen\u002Fblog\u002F1tool-api-documentation-openapi-live.md","The 1Tool API: more than 2,500 endpoints, documented live",{"type":7,"value":8,"toc":107},"minimark",[9,13,18,21,25,33,37,40,44,69,73,84,90,93],[10,11,12],"p",{},"Anyone planning an integration with a CRM or ERP system sooner or later faces a crucial question: how reliable is the available API documentation really? With many providers, hand-maintained documentation goes out of date as soon as something changes in the interface behind the scenes – new fields, changed endpoints, adjusted parameters. At 1Tool, this problem is solved structurally: the documentation is not written separately from the code, but generated directly from the code at runtime.",[14,15,17],"h2",{"id":16},"more-than-2500-endpoints-for-almost-every-area-of-the-software","More than 2,500 endpoints for almost every area of the software",[10,19,20],{},"The 1Tool platform is based on a REST API with more than 2,500 individual routes in total. This scale shows how deeply the API reaches into the actual functionality of the software: almost every area visible in the user interface can also be controlled programmatically. For companies planning an integration, this is an important difference from systems that offer only a thin API layer added as an afterthought.",[14,22,24],{"id":23},"documentation-that-comes-from-the-code-itself","Documentation that comes from the code itself",[10,26,27,28,32],{},"The decisive point, however, is not the sheer number of endpoints but how the accompanying documentation is created. Instead of maintaining a separate text file or wiki alongside the code, 1Tool generates the API description automatically from the actual implementation – in the widely used OpenAPI standard format. This means that every change to an endpoint, every new field and every adjusted parameter automatically flows into the documentation without anyone having to update it manually. Documentation and implementation simply cannot drift apart.\nFor developers and technical contacts on the customer side, there is also an interactive Swagger interface at ",[29,30,31],"em",{},"\u002Fapi\u002Fdocs"," , where endpoints can be tried out directly in the browser. This lets you test a request before writing a single line of integration code.",[14,34,36],{"id":35},"conceptual-guides-for-more-complex-topics","Conceptual guides for more complex topics",[10,38,39],{},"Pure endpoint references answer the question “Which parameters does this endpoint accept?”, but not always the question “How do several endpoints work together to achieve a goal?”. That is why 1Tool also provides separate conceptual guides – for example on custom fields, filter mechanisms or workflows. These guides complement the purely technical reference with the business context you need for a clean integration.\nFor IT decision-makers evaluating an integration, this difference is more than a formality. Hand-maintained documentation is only ever as current as the person who last edited it – and in practice, documentation discipline loses out to release pressure. Documentation generated from the code does not have this problem: by definition it is as current as the production version of the software. Anyone building an integration that is meant to run reliably for months or years benefits directly from the fact that the reference they rely on cannot become outdated.",[14,41,43],{"id":42},"frequently-asked-questions","Frequently asked questions",[10,45,46,50,53,54,57,59,60,63,65,66],{},[47,48,49],"strong",{},"Do I have to register before using the API documentation?",[51,52],"br",{},"\nThe interactive documentation is available at \u002Fapi\u002Fdocs. For actual test calls against real data, valid authentication is required, as with any REST API.\n",[47,55,56],{},"Will an existing integration remain stable even as the 1Tool API evolves?",[51,58],{},"\nYes. New functions extend the API without changing existing endpoints, so running integrations are not affected by further development.\n",[47,61,62],{},"Where can I find information that goes beyond individual endpoints, for example on workflows or filters?",[51,64],{},"\nThere are dedicated conceptual guides for this, maintained independently of the pure endpoint reference, which explain the business context.\n",[47,67,68],{},"How well would automatically generated, always up-to-date API documentation suit your next integration project?",[14,70,72],{"id":71},"read-more","Read more",[74,75,76],"ul",{},[77,78,79],"li",{},[80,81,83],"a",{"href":82},"\u002Fen\u002Fblog\u002Fdatabase-per-tenant-multi-tenancy-1tool\u002F","Database per tenant: how 1Tool really solves multi-tenancy",[10,85,86],{},[80,87,89],{"href":88},"\u002Fen\u002Fappointment-request\u002F","Book a demo",[14,91,72],{"id":92},"read-more-1",[74,94,95,101],{},[77,96,97],{},[80,98,100],{"href":99},"\u002Fen\u002Fblog\u002Fai-agents-automated-document-processing\u002F","AI agents behind the scenes: automated document processing",[77,102,103],{},[80,104,106],{"href":105},"\u002Fen\u002Fblog\u002Fwebsocket-infrastructure-real-time-1tool\u002F","Real-time updates without detours: the WebSocket infrastructure behind 1Tool",{"title":108,"searchDepth":109,"depth":109,"links":110},"",2,[111,112,113,114,115,116],{"id":16,"depth":109,"text":17},{"id":23,"depth":109,"text":24},{"id":35,"depth":109,"text":36},{"id":42,"depth":109,"text":43},{"id":71,"depth":109,"text":72},{"id":92,"depth":109,"text":72},[118],3330,"2026-06-26T09:00:00",false,null,"md","\u002Fmedia\u002F2026\u002F07\u002F1tool-api-dokumentation-openapi-live.jpg","en",{},"2026-07-25T08:25:42",true,"\u002Fen\u002Fblog\u002F1tool-api-documentation-openapi-live",{"title":5,"description":12},"More than 2,500 API endpoints, generated automatically from the code: the live OpenAPI documentation and Swagger UI of 1Tool.","The 1Tool API: 2,500+ endpoints, documented live | 1Tool","1tool-api-documentation-openapi-live","\u002Fen\u002Fblog\u002F1tool-api-documentation-openapi-live\u002F","en\u002Fblog\u002F1tool-api-documentation-openapi-live","posts","F_6HW4dDe3ydrM7JzgXYztTjVD0ujHWTFHX9b5M0PXk",1791581805027]