canonical: https://jentic.com/apis/nasajon.app/nasajon

# Nasajon App APIs do Web Report

The Web Report API from Nasajon generates formatted reports from configured data sources and layouts. It registers database connections, defines JSON and database data sources, stores saved queries and report layouts, then runs report jobs and returns their output by job id. Teams use it to turn structured business data into on-demand report documents.

## For AI agents

Define data sources, queries, and layouts, then generate reports and poll each report job for its output. Built around saved connections and reusable report templates.

## Scope

Does not handle data warehousing, live dashboards, or report email delivery. Use for generating formatted reports from configured data sources only.

## Capabilities

- Register database connections the report engine will query
- Define saved queries that pull the rows a report needs
- Configure JSON and database data sources for report layouts
- Build and store report layouts that bind data to a template
- Run report jobs and poll each job by its id for the finished output
- Retrieve a report job's status and output once rendering completes

## Use cases

### AI Reporting Agent

An AI agent connected through Jentic produces a business report on request by selecting a saved query and layout, submitting the report job, and polling it until the output is ready, so a user asking for a monthly summary gets a finished document without the developer sequencing the calls by hand. The agent reuses the data sources and layouts already configured in the account.

Example prompt: Submit a report job for the monthly sales layout against its data source, then poll the job id and return the finished output

### Scheduled Document Rendering

A back-office product renders recurring documents by storing a layout and query once and triggering a report job on a schedule. Because each job is tracked by its id, the product can fire many renders and collect the outputs asynchronously as they complete rather than blocking on each one.

Example prompt: Trigger report jobs for a list of saved layouts and collect each finished output by polling its job id

### Data Source Management

An operations tool wires new reports to live data by registering a database connection, defining a JSON or database data source over it, and binding that source into a report layout. Connections and data sources are addressed by id so a single source can back many layouts and report runs.

Example prompt: Register a database connection, define a data source over it, and bind the source into a new report layout

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/reports` | List report definitions |
| POST | `/reports` | Submit a report run |
| GET | `/reports/jobs/{id}` | Get a report job's status and output |
| GET | `/consultas` | List saved queries |
| GET | `/datasources` | List configured data sources |
| GET | `/layouts` | List report layouts |
| GET | `/conexoes` | List database connections |

## Key resources

- **Connections** — Database connections the report engine queries
- **Queries** — Saved queries that return the rows for a report
- **Data Sources** — JSON and database data sources bound into layouts
- **Layouts** — Report templates that bind data to a document design
- **Reports** — Report runs and their asynchronous jobs, tracked by job id

## 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:** 37 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 17 / 100
  - Agent Usability: 94 / 100
  - Security: 30 / 100
  - AI Discoverability: 50 / 100
- **View full report:** https://jentic.com/apis/nasajon.app/nasajon/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 Web Report API by hand means implementing its OAuth2 password flow, managing tokens with the offline_access scope, and sequencing the data-source, layout, and report-job calls yourself. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Reports read from the sources you connect, so a rule can give the agent just the query and report-generation operations and leave connection and data-source changes out. You choose which operations it may call.
- **Credential handling:** Your Web Report OAuth2 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.
- **Discovery method:** Agents search Jentic by intent such as 'generate a report' or 'list the saved queries', and Jentic returns the matching Web Report operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Metabase API** — Open-source business intelligence with queries, questions, and dashboards.
- **Geckoboard API** — Dashboard service for pushing metrics onto live display boards.
- **Zoho Sheet API** — Spreadsheet API that can supply or receive the data behind a report.

## FAQ

### What authentication does the Web Report API use?

The Web Report API uses OAuth2 with the password flow and an offline_access scope, per its OpenAPI spec, so your client exchanges credentials for a bearer token and refreshes it as needed. Through Jentic that token is held encrypted by your own Jentic One instance and injected at call time.

### Can I generate a report with the Web Report API?

Yes. You submit a report request against a configured layout and data source, then poll the report job by its id until the output is ready. Saved queries and data sources are defined once and reused across report runs, so a single request kicks off the render.

### Can I manage data sources with the Web Report API?

Yes. The API registers database connections and both JSON and database data sources, which report layouts then bind to. Each data source is addressed by its id so one source can back many layouts and report jobs.

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

Yes. Write a rule that allows only the query and report-generation operations, so the agent runs and fetches reports while connection, data-source, and layout changes stay out of its reach unless you add them. Every call the agent makes is logged.

### How do I generate a report with the Web Report API through Jentic?

Search by intent in Jentic with a query like 'generate a Web Report', add the Web Report API from the Jentic API Directory, and your agent submits the report request then polls the job id for the finished output. To run it on your own infrastructure, install Jentic One from its GitHub repo.