canonical: https://jentic.com/apis/swaggerhub.acce28/acclake-api

# Acce28 ACCLAKE-api

ACCLAKE-api provides programmatic access to developer tools functionality. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically post-indireto-extract-create, post-indireto-extract-status. Covers 2 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- post-indireto-extract-create
- post-indireto-extract-status
- Integrate ACCLAKE-api into automated workflows
- Query and filter ACCLAKE-api records by parameters
- Monitor ACCLAKE-api operational status and events

## Use cases

### Developer Tools Operations

Use the ACCLAKE-api to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including post-indireto-extract-create, post-indireto-extract-status.

Example prompt: Call POST /indireto/extract/create to post-indireto-extract-create

### Data Retrieval and Monitoring

Query ACCLAKE-api resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary ACCLAKE-api endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call ACCLAKE-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 apiKey tokens manually.

Example prompt: Search Jentic for 'post-indireto-extract-create', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /indireto/extract/create | post-indireto-extract-create |
| POST | /indireto/extract/status | post-indireto-extract-status |

## Key resources

- **indireto** — Operations related to indireto

## Why Jentic

- **Setup:** Wiring the ACCLAKE API by hand means attaching its Accera-Key header to every request against the sandbox AWS execute-api host and tracking extract creation and status yourself. Through Jentic you install once, import the ACCLAKE API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Both ACCLAKE operations carry their targets in the request body, so scope your agent to the operations it needs, such as creating an extract or checking extract status. You choose that set, so nothing beyond the operations you allow is included.
- **Credential handling:** Your ACCLAKE Accera-Key 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 'create an extract' or 'check extract status', and Jentic returns the matching ACCLAKE operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the ACCLAKE-api use?

The ACCLAKE-api uses an API key passed in the `Accera-Key` 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 post-indireto-extract-create with the ACCLAKE-api?

Yes. Use the POST /indireto/extract/create endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the ACCLAKE-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 post-indireto-extract-create through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'post-indireto-extract-create'. Jentic returns the matching ACCLAKE-api operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the ACCLAKE-api have?

The ACCLAKE-api exposes 2 endpoints covering indireto operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which ACCLAKE operations and credentials the agent may use. The ACCLAKE API has just two operations, creating an extract and checking extract status, and since both carry their targets in the request body you scope the agent to only the ones it needs. If you grant only status checks, the agent cannot create extracts, and nothing beyond the operations you allow is available to it.