canonical: https://jentic.com/apis/swaggerhub.generixgroup8/afnor-flow-service

# Generixgroup8 AFNOR Flow Service

The __Flow Service API__ allows to: - Upload a flow. - Retrieve information related to a set of flows. - Download a flow given its identifier The resources of the API are : - `/flows` : with creation and retrieval methods. - `/webhooks` : creation, update, delete, list Worflow example: - `POST /flows` : provide the flow information & content - `POST /flows/search` : retrieve flows given multiple c. The API exposes 9 endpoints secured with bearer, oauth2 authentication.

## For AI agents

Programmatically submit a new flow, select flows upon criteria. Covers 9 operations with bearer, oauth2 authentication.

## Scope

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

## Capabilities

- Submit a new flow
- Select flows upon criteria
- Download the file of a flow
- Subscribe to a webhook
- Retrieve the list of webhooks created by the owner of the token
- Get a webhook content
- Update a webhook subscription

## Use cases

### Developer Tools Operations

Use the AFNOR Flow Service to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including submit a new flow, select flows upon criteria, download the file of a flow.

Example prompt: Call POST /v1/flows to submit a new flow

### Automated Flow Management

Automate flow operations by combining multiple AFNOR Flow Service endpoints. Agents can select flows upon criteria and then download the file of a flow in a single workflow.

Example prompt: Call POST /v1/flows/search to select flows upon criteria, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call AFNOR Flow Service 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 bearer, oauth2 tokens manually.

Example prompt: Search Jentic for 'submit a new flow', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/flows | Submit a new flow |
| POST | /v1/flows/search | Select flows upon criteria |
| GET | /v1/flows/{flowId} | Download the file of a flow |
| POST | /v1/webhooks | Subscribe to a webhook |
| GET | /v1/webhooks | Retrieve the list of webhooks created by the owner of the token |
| GET | /v1/webhooks/{webhookUid} | Get a webhook content |
| PATCH | /v1/webhooks/{webhookUid} | Update a webhook subscription |
| DELETE | /v1/webhooks/{webhookUid} | Unsubscribe to a webhook |

## Key resources

- **Flow** — Flow management
- **Supervisor** — Service supervision
- **Webhook** — Webhook management

## Why Jentic

- **Setup:** Wiring the AFNOR Flow Service by hand means resolving its templated sub-domain and domain host, choosing between the JWT bearer and OAuth 2.0 client credentials schemes, and running the token exchange yourself. Through Jentic you install once, import AFNOR Flow Service from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** The Flow Service puts the webhook id in the URL path (/v1/webhooks/{webhookUid}), so a rule can pin your agent to one webhook: it can read that webhook and nothing else. You choose the operations it may call, so state-changing ones like patching or deleting a webhook are not included unless you add them.
- **Credential handling:** Your AFNOR bearer token or OAuth client credentials 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 'submit a new flow' or 'register a webhook', and Jentic returns the matching AFNOR Flow Service 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 AFNOR Flow Service use?

The AFNOR Flow Service uses bearer, oauth2 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 submit a new flow with the AFNOR Flow Service?

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

### What are the rate limits for the AFNOR Flow Service?

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 submit a new flow through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'submit a new flow'. Jentic returns the matching AFNOR Flow Service operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the AFNOR Flow Service have?

The AFNOR Flow Service exposes 9 endpoints covering flow, supervisor, webhook operations.

### Can I limit what my agent is allowed to do with the AFNOR Flow Service?

Yes. Jentic One is self-hosted, so your own rules decide which AFNOR Flow Service operations and credentials the agent may use. You pick the exact endpoints it can call, so read-only work like GET /v1/flows/{flowId} or GET /v1/webhooks stays available while state-changing calls such as PATCH or DELETE /v1/webhooks/{webhookUid} are excluded unless you add them. Because the webhook id lives in the URL path, a rule can also pin the agent to a single webhook so it reads that one and nothing else.