The __Directory Service__ API allows you to: - View and search for companies (SIREN) - View and search for establishments (SIRET) - View, and search for routing codes - View, and search for directory entries **Authentication :** Each endpoint must be called with an access token (Bearer). This token is retrieved by a call to a token URL. --- Siren Company by Siren number - `POST /siren/search` => S. The API exposes 9 endpoints secured with bearer, oauth2 authentication.
9 endpointsThe __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.
9 endpointsStep 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 | shStep 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 instanceJentic 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.