canonical: https://jentic.com/apis/mighty-office.com/mighty-office

# Mighty Office Mighty API

The Mighty API gives non-human clients programmatic access to Mighty-Office features. It reads a form's fields including its subform fields, reads a single form answer with its subform answers, and creates new form answers against a form. It also exports a report's output as JSON, uploads a staging CSV file or attaches an image or document to an object, and fetches raw images and documents by token.

## For AI agents

Read form fields, read and create form answers, export report output as JSON, and upload files or attachments to Mighty-Office objects. Built for non-human clients of Mighty-Office.

## Scope

Does not design forms, manage user accounts, or send notifications. Use for reading form fields, reading and creating form answers, exporting reports, and uploading files only.

## Capabilities

- Read a form's fields, including its subform fields
- Read a single form answer with its subform answers
- Create a form answer against a form
- Export a report's output as JSON
- Upload a staging CSV file or attach an image or document to an object
- Fetch a raw image or document by its token

## Use cases

### Agent form submission

An AI agent collecting structured input reads a form's fields to learn what is required, then creates a form answer with the values it gathered. The Mighty API returns the field definitions, including subform fields, and accepts a new form answer against the form, so the agent can fill and submit a form end to end. Through Jentic the operations are discovered by intent and the token is injected at call time.

Example prompt: Read a form's fields, then create a form answer that supplies a value for each required field

### Report export to JSON

Teams need a report's data in a machine-readable shape for downstream processing. The Mighty API exports a report's output as JSON by report id, so an agent can pull a report and hand its rows to another system without scraping a rendered page.

Example prompt: Export a report's output as JSON for a given report id and pass the rows to a downstream step

### File and attachment upload

Workflows often attach supporting files to a record. The Mighty API uploads a staging CSV file and attaches an image or document to an object, and lets a client fetch raw images or documents back by token, so an agent can push a file into Mighty-Office and retrieve it later.

Example prompt: Attach a document to an object and then fetch the raw file back by its token to confirm the upload

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/de/api/user/login` | Log in and obtain a token |
| GET | `/de/api/form/getfields/{formId}/{includeSubformFields}` | Get a form's fields |
| GET | `/de/api/formanswer/read/{formId}/{formanswerId}/{includeSubformAnswers}` | Read a single form answer |
| POST | `/de/api/formanswer/create/{formId}` | Create a form answer |
| GET | `/de/reportexport/json/{reportId}` | Export a report's output as JSON |
| POST | `/de/api/file/upload` | Upload a staging CSV file |

## Key resources

- **Forms** — Read a form's fields, including its subform fields
- **Form Answers** — Read a single form answer and create new form answers against a form
- **Reports** — Export a report's output as JSON by report id
- **Files** — Upload a staging CSV, attach an image or document to an object, and fetch raw files by token

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 57 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 66 / 100
  - AI-Readiness & Agent Experience: 36 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 46 / 100
- **View full report:** https://jentic.com/apis/mighty-office.com/mighty-office/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Mighty API by hand means calling the login operation to mint a JWT, sending it as a bearer token on later calls, and handling the form-id path structure and file uploads yourself. Through Jentic you install once, import it from the API Directory, store the login credential once, and your agent calls it.
- **Permission scoping:** Mighty puts the form id in the URL path, so a rule can pin your agent to the operations and forms you pick: it can read fields and create answers for one form. You choose the operation set, so the file-upload operations are not included unless you add them.
- **Credential handling:** Your Mighty login credential is stored once, encrypted, by your own Jentic One instance and the token is injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a form answer' or 'export a report', and Jentic returns the matching Mighty operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Typeform** — Typeform builds conversational forms and returns their responses through an API.
- **Jotform** — Jotform creates forms and reads their submissions over an API.
- **Formstack** — Formstack manages forms, workflows, and documents.

## FAQ

### What authentication does the Mighty API use?

The Mighty API uses a JWT bearer token, per its OpenAPI spec: a login operation returns the token, which later calls send in the Authorization header. Through Jentic the credential is stored once and the token is injected at call time, so it never enters the agent's prompt, logs, or context.

### Can I create form answers with the Mighty API?

Yes. A create operation accepts a new form answer against a specific form id, and a read operation returns a single answer with its subform answers. An agent can read the form's fields first to learn what is required, then submit a complete answer.

### What are the rate limits for the Mighty API?

The OpenAPI spec does not define numeric rate limits. Have your agent back off when it receives an HTTP 429 response, and contact Mighty-Office for the limits that apply to your account.

### Is there a Mighty Office MCP server?

You don't need an MCP server to give your agent the Mighty API. Jentic connects it directly from the API Directory: import it, store your login credential once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

### Can I limit what my agent is allowed to do with the Mighty API?

Yes. Mighty puts the form id in the URL path, such as the form-fields and form-answer operations, so a rule can pin your agent to the operations and forms you pick, letting it read fields and create answers without the file-upload operations unless you add them. Every call it makes is logged.

### How do I submit a form answer through Jentic?

Search Jentic for an intent such as 'create a new form answer' and it returns the matching create operation with its input schema, so your agent reads the form fields, assembles the values, and submits the answer. To run it on your own infrastructure, install Jentic One from its GitHub repo.