Tally So Tally API
Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer29 EndpointsREST
For Agents
Programmatically create a new form, retrieve a list of forms. Covers 29 operations with bearer authentication.
Use for: I need to a new form, I want to a list of forms, Search for a form, Find all a form
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Tally API provides programmatic access to developer tools functionality. The API exposes 29 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Tally API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tally API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftally.so%2Ftally-so" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftally.so%2Ftally-so" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Tally API.
Create a new form
Retrieve a list of forms
Update a form
Delete a form
Monitor Tally API operational status and events
Use Cases
Patterns agents use Tally API for, with concrete tasks.
★ Developer Tools Operations
Use the Tally API to perform developer tools operations programmatically. The API provides 29 endpoints covering core functionality including create a new form, retrieve a list of forms, retrieve a form.
Call POST /forms to create a new form
Automated Forms Management
Automate forms operations by combining multiple Tally API endpoints. Agents can retrieve a list of forms and then retrieve a form in a single workflow.
Call GET /forms to retrieve a list of forms, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Tally API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'create a new form', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
29 endpoints — tally api provides programmatic access to developer tools functionality.
METHOD
PATH
DESCRIPTION
POST
/forms
Create a new form
GET
/forms
Retrieve a list of forms
GET
/forms/{formId}
Retrieve a form
PATCH
/forms/{formId}
Update a form
DELETE
/forms/{formId}
Delete a form
GET
/users/me
Retrieve current user information
POST
/workspaces
Create a new workspace
GET
/workspaces
Retrieve a list of workspaces
POST
/forms
Create a new form
GET
/forms
Retrieve a list of forms
GET
/forms/{formId}
Retrieve a form
PATCH
/forms/{formId}
Update a form
DELETE
/forms/{formId}
Delete a form
GET
/users/me
Retrieve current user information
POST
/workspaces
Create a new workspace
GET
/workspaces
Retrieve a list of workspaces
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Tally API by hand means setting up bearer token auth, sending it on every call, and shaping its form and workspace routes yourself. Through Jentic you install once, import the Tally API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Tally puts the form id in the URL path (/forms/{formId}), so a rule can pin your agent to one form: it can read that form and nothing else. You choose the operations it may call, so updating or deleting a form is not included unless you add it.
Credential isolation
Your Tally token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a new form' or 'list workspaces', and Jentic returns the matching Tally operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Tally API through Jentic.
What authentication does the Tally API use?
The Tally API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create a new form with the Tally API?
Yes. Use the POST /forms endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Tally API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create a new form through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new form'. Jentic returns the matching Tally API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Tally API have?
The Tally API exposes 29 endpoints covering forms, organizations, users operations.
Can I limit what my agent is allowed to do with the Tally API?
Yes. Jentic One is self-hosted, so your own rules decide which Tally operations and credentials the agent may use. Because Tally puts the form id in the URL path (/forms/{formId}), a rule can pin the agent to a single form so it reads that form and nothing else. You also choose the operations it may call, so updating or deleting a form (PATCH or DELETE /forms/{formId}) or creating workspaces is excluded unless you explicitly grant it.
GET STARTED