canonical: https://jentic.com/apis/swaggerhub.sensusx/sensus-rest-api-projects

# Sensusx Sensus REST API projects

Apresentação Documentação para utilização da REST API Sensus Customers. Autenticação É necessário uma chave/token como Header para autenticar e fazer requisições a esta API. O nome do Header da chave/token é 'x_api_key'. Para gerar a chave/token da sua organização: 1) Faça login no <a href="https://app.sensusonline.net/sensus/" target="_blank">Sensus CRM</a> 2) Navegue Home/Configurar/Organização . The API exposes 4 endpoints.

## For AI agents

Programmatically query projects by creation date, query projects by project name. Covers 4 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Query projects by creation date
- Manage identity auth data programmatically
- Integrate Sensus REST API projects into automated workflows
- Query and filter Sensus REST API projects records by parameters
- Monitor Sensus REST API projects operational status and events

## Use cases

### Identity and Authentication Operations

Use the Sensus REST API projects to perform identity auth operations programmatically. The API provides 4 endpoints covering core functionality including query projects by creation date, query projects by project name, query projects by project id.

Example prompt: Call GET `/created/{creation_date}` to query projects by creation date

### Automated Projects Management

Automate projects operations by combining multiple Sensus REST API projects endpoints. Agents can query projects by project name and then query projects by project id in a single workflow.

Example prompt: Call GET `/project/{project_name}` to query projects by project name, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sensus REST API projects 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 none tokens manually.

Example prompt: Search Jentic for 'query projects by creation date', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/created/{creation_date}` | Query projects by creation date |
| GET | `/project/{project_name}` | Query projects by project name |
| GET | `/tasks/{project_id}` | Query projects by project id |
| GET | `/updated/{update_date}` | Query projects by update date |

## Key resources

- **Projects** — Operations related to Projects

## Why Jentic

- **Setup:** Wiring the Sensus REST API projects endpoints by hand means reading Sensus docs, targeting the app.sensusonline.net project host, and writing your own request and retry handling even though the endpoints are open. Through Jentic you install once, import Sensus REST API projects from the API Directory, store any needed access detail once, and your agent calls it.
- **Permission scoping:** This API puts the project in the URL path (`/project/{project_name}`, `/tasks/{project_id}`), so a rule can pin your agent to reads for one project: it can look up that project and its tasks and nothing else. You choose the operations it may call, so the by-creation-date and by-update-date lookups are not included unless you add them.
- **Credential handling:** Any Sensus REST API projects access detail 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 'find a Sensus project by name' or 'list tasks for a project', and Jentic returns the matching Sensus REST API projects operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Sensus REST API projects use?

The Sensus REST API projects uses no authentication. 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 query projects by creation date with the Sensus REST API projects?

Yes. Use the GET `/created/{creation_date}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Sensus REST API projects?

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 query projects by creation date through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'query projects by creation date'. Jentic returns the matching Sensus REST API projects operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Sensus REST API projects have?

The Sensus REST API projects exposes 4 endpoints covering projects operations.

### Can I limit what my agent is allowed to do with the Sensus REST API projects?

Yes. Jentic One runs self-hosted, so you set the rules that decide which Sensus operations and credentials your agent may use. Because this API puts the project in the URL path, such as GET `/project/{project_name}` and GET `/tasks/{project_id}`, you can pin the agent to reading one named project and its tasks and nothing else. Since you pick the operations it may call, the by-creation-date and by-update-date lookups stay unavailable unless you explicitly add them.