canonical: https://jentic.com/apis/swaggerhub.myself446/c

# Myself446 Cервис акций

Апи сервиса Акций РО: Кривцова Юлия Разработчики: Маслов Максим, Марамыгин Алексей Тестовые данные: Запускать локально после миграции для создания тестовых данных class TestDevValues метод test_dev_values. The API exposes 11 endpoints.

## For AI agents

Programmatically обновить оргструктуры, получить оргструктуру. Covers 11 operations.

## Scope

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

## Capabilities

- Обновить оргструктуры
- Получить оргструктуру
- Создать/обновить параметры шаблона акции
- Доп виды условий в шаблоне акции
- Monitor Cервис акций operational status and events

## Use cases

### Developer Tools Operations

Use the Cервис акций to perform developer tools operations programmatically. The API provides 11 endpoints covering core functionality including обновить оргструктуры, получить оргструктуру, создать/обновить параметры шаблона акции.

Example prompt: Call POST /sync_orgstructures to обновить оргструктуры

### Automated orgstructures Management

Automate orgstructures operations by combining multiple Cервис акций endpoints. Agents can получить оргструктуру and then создать/обновить параметры шаблона акции in a single workflow.

Example prompt: Call POST /get_orgstructure to получить оргструктуру, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Cервис акций 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 'обновить оргструктуры', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/sync_orgstructures` | Обновить оргструктуры |
| POST | `/get_orgstructure` | Получить оргструктуру |
| POST | `/update_promo_template` | Создать/обновить параметры шаблона акции |
| POST | `/get_promo_templates` | Получить шаблоны акции или указанную по ключу |
| POST | `/update_promo_conditions` | Доп виды условий в шаблоне акции |
| POST | `/update_promo_goods` | Создать/обновить товары, для срабатывания шаблона акции. Если код товара задать |
| POST | `/update_promo_prize` | Создать/обновить призы шаблона акции |
| POST | `/update_promotion` | Создать/обновить параметры акции |

## Key resources

- **orgstructures** — Оргструктура
- **promo_template** — Шаблон акции
- **promotion_action** — Акция

## Why Jentic

- **Setup:** Wiring the promotions admin service by hand means mapping its org-structure and promo-template routes, coding each POST, and handling retries yourself. Through Jentic you install once, import the promotions admin service from the API Directory, store any host details once, and your agent calls it.
- **Permission scoping:** This service carries its promotion and org-structure targets in the request body rather than the URL path, so scope the agent to the operations it needs, such as reading promo templates. You choose the operations it may call, so write operations like updating a promotion are not included unless you add them.
- **Credential handling:** Any access details for the promotions admin service are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'sync org structures' or 'read promo templates', and Jentic returns the matching promotions admin 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 Cервис акций use?

The Cервис акций 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 обновить оргструктуры with the Cервис акций?

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

### What are the rate limits for the Cервис акций?

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 обновить оргструктуры through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'обновить оргструктуры'. Jentic returns the matching Cервис акций operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Cервис акций have?

The Cервис акций exposes 11 endpoints covering orgstructures, promo_template, promotion_action operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which of this service's operations the agent may call and which credentials it may use. This API carries its promotion and org-structure targets in the request body rather than the URL path, so you scope access at the operation level: you can allow read calls such as POST /get_promo_templates and POST /get_orgstructure while withholding write calls such as POST /update_promotion or POST /sync_orgstructures. Any operation you do not grant stays unavailable to the agent.