Endpoints
Accessible routes, expected parameters and usable responses.
API & connecteurs
Open your internal systems without opening your entire system.
Integrations cover market tools. APIs and connectors cover what is specific to each company: in-house tools, business data, internal workflows and systems already in place.
API & connecteurs
What the page details
A connector is an operational contract.
Operational contract
A connector is an operational contract.
It defines what an autonomous employee can request, read, prepare or trigger. Nothing is implicit: each possible action must be described, authorized and observable.
Permissions
The rights granted according to the role, context, team or customer scope.
Actions
What can be read, created, modified, sent, planned or simply suggested.
Traces
Calls, sources, errors, validations and exceptions retained for audit.
Life cycle
From the internal system to the controlled connector.
Frame
Identify the system, use cases, necessary data and sensitive actions.
Describe
Provide API documentation, data schemas, business rules and access limits.
Build
Prepare the connector, scopes, error messages and necessary validations.
Test
Simulate calls, check permissions and isolate ambiguous cases before production.
Supervise
Track uses, failures, validations and actions actually triggered.
Controls
The connector limits autonomy instead of expanding it without control.
Atlensia does not seek to provide global access to internal systems. The objective is to create a controlled interface between autonomous employees and company tools.
Scopes
An autonomous employee only accesses the routes useful to his role.
Validation
Sensitive writings, sendings or decisions may require human approval.
Partitioning
Data can remain separated by team, entity, customer or environment.
Observability
Every important call remains legible: who, what, why, with what source.
Specific systems
Connectors are mainly used where your tools are specific.
Internal ERP
Read a file status, prepare an update or trigger a validation request.
Documentary base
Search for a procedure, find a document, cite a source or prepare a summary.
Customer portal
Qualify a request, prepare a response or report an anomaly to the right person.
Business reporting
Retrieve indicators, detect a gap and prepare an actionable comment.
Preparation
What Atlensia needs to build properly.
API documentation or access diagram.
The roles that will have the right to use the connector.
Accessible data and prohibited data.
Free, validated or prohibited actions.
A testing environment when the action can modify data.
Escalation rules in case of error or ambiguity.
Next step
Once the systems are connected, you must choose the right models for the right uses.
Performance, cost, sovereignty, confidentiality, latency: Atlensia can orchestrate several providers depending on the context.