Build with Tale
Connect another system to Tale, automate a workflow, or contribute to the application source.
2 min read
Use these guides when writing a client, connecting an external system, or changing Tale itself. Start with the smallest working request, then add the authentication, scope, and recovery handling your integration needs.
Choose a development task
| What you want to build | Start here |
|---|---|
| A script that sends a message and reads the reply | Call Tale from a script |
| A client for projects, tasks, files, or other resources | API reference |
| A connection from an MCP client | MCP endpoint |
| AI help in your editor, with Tale's knowledge or models | Use Tale from your editor or a script |
| An automation triggered by another system | Webhooks |
| A filesystem client for documents | WebDAV API |
| A new connector | Connector development |
| A change to Tale's application code | Contributor setup |
Make the first request reliable
Choose the credential with the surface: REST and MCP use API keys, WebDAV uses an app password, and a webhook uses a secret trigger URL. These credentials are not interchangeable.
Create a separate API key for each integration, send it only to the intended instance, and keep it out of source control. Make your first API request explains instance URLs and organization scope. For a long-running operation, distinguish the accepted request from its eventual result: poll the resource or run and handle a failed outcome.
Read the rate limits before adding retries. Check instance availability when troubleshooting a connection. The API reference describes the error envelope and the generated specification for the current checkout.
Build inside the platform
For agents, projects, and the automation editor, use the Developer guide. AI-assisted development explains how to combine authoring tools with validation and review.