canonical: https://jentic.com/apis/swaggerhub.sensusx/sensus-rest-api-customers # Sensusx Sensus REST API customers 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 Sensus CRM 2) Navegue Home/Configurar/Organização . The API exposes 3 endpoints. ## For AI agents Programmatically query customers by creation date, query customers by name. Covers 3 operations. ## Scope Does not handle payments, communications, or crm - use for identity and authentication only. ## Capabilities - Query customers by creation date - Manage identity auth data programmatically - Integrate Sensus REST API customers into automated workflows - Query and filter Sensus REST API customers records by parameters - Monitor Sensus REST API customers operational status and events ## Use cases ### Identity and Authentication Operations Use the Sensus REST API customers to perform identity auth operations programmatically. The API provides 3 endpoints covering core functionality including query customers by creation date, query customers by name, query customers by update date. Example prompt: Call GET `/created/{creation_date}` to query customers by creation date ### Automated Customers Management Automate customers operations by combining multiple Sensus REST API customers endpoints. Agents can query customers by name and then query customers by update date in a single workflow. Example prompt: Call GET `/customer/{customer_name}` to query customers by name, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Sensus REST API customers 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 customers by creation date', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/created/{creation_date}` | Query customers by creation date | | GET | `/customer/{customer_name}` | Query customers by name | | GET | `/updated/{update_date}` | Query customers by update date | ## Key resources - **Customers** — Operations related to Customers ## Why Jentic - **Setup:** Wiring Sensus REST API customers by hand means standing up its app.sensusonline.net host and handling requests and retries yourself, even though it ships no auth scheme. Through Jentic you install once, import Sensus REST API customers from the API Directory, store any connection details once, and your agent calls it. - **Permission scoping:** Sensus REST API customers puts the customer name in the URL path (`/customer/{customer_name}`), so a rule can pin your agent to one customer: it can read that customer and nothing else. Every operation here is read-only, so no write reaches your data regardless. - **Credential handling:** Any Sensus REST API customers connection 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 'query customers by creation date' or 'look up a customer by name', and Jentic returns the matching Sensus REST API customers 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 customers use? The Sensus REST API customers 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 customers by creation date with the Sensus REST API customers? 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 customers? 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 customers 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 customers by creation date'. Jentic returns the matching Sensus REST API customers operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Sensus REST API customers have? The Sensus REST API customers exposes 3 endpoints covering customers operations. ### Can I limit what my agent is allowed to do with the Sensus REST API customers? Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations your agent may call and which connection details it can use. Since the customer name sits in the URL path (GET `/customer/{customer_name}`), you can pin the agent to a single customer so it reads that record and nothing else, and you can allow only specific operations such as the created-date or updated-date lookups. Every operation here is read-only, so the agent cannot write to your data even when a call is permitted.