Generixgroup8 AFNOR Flow Service

Name: AFNOR Flow Service API
Brand: AFNOR Flow Service
Availability: InStock

Browse all Swaggerhub Generixgroup8 APIs

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbearer, oauth29 Endpoints

Install Jentic One Beta

Connect the AFNOR Flow Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AFNOR Flow Service, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AFNOR Flow Service API.

Submit a new flow

Select flows upon criteria

Download the file of a flow

Subscribe to a webhook

GET STARTED

Start building with AFNOR Flow Service API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to submit a new flow, I want to select flows upon criteria, Search for download the file of a flow, Find all subscribe to a webhook

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

Use Cases

Patterns agents use AFNOR Flow Service API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

9 endpoints — the __flow service api__ allows to: - upload a flow.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using AFNOR Flow Service API through Jentic.

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.