Use cases
Connect your systems via API
For systems without a dedicated connector: Gescon talks to your API following the contract you define.
Engineering
«Can Gescon query our internal orders API?»
Yes, if the endpoint and credentials are defined: Gescon only calls what you authorise.
Product
«What endpoints does this integration have active?»
Gescon lists the configured endpoints and what each one is used for.
Support
«Why did this API call fail?»
Returns the error code and the exact response the system gave.
Management
«How many custom integrations do we have active?»
A list of the connected APIs and since when.
What it brings
What it reads and what it doesn't touch
The connector can only call the endpoints you define. Gescon doesn't widen your API's contract.

- Endpoints you authoriseNot one more: the rest of your API is invisible to Gescon.
- Parameters for each callEvery request is logged with what was sent.
- The system's exact responseShown exactly as your API returns it, without reinterpreting it.
- Citations to the source endpointEvery answer indicates which endpoint generated it.
- No added permissionsIf your API doesn't allow writing, neither can Gescon.
Setup
Your contract, its rules
- Define the endpointThe base URL and the resources Gescon will be able to query.
- Authorise the connectionWith the API key or the authentication scheme you use.
- Validate with three questionsCheck the exact response before opening it to the team.
Requirements
- Endpoint reachable from Gescon
- Credentials or API key with read permissions
- Minimal documentation of the contract (request and response schema)
Estimated connection time: varies by API
Same family
SharePoint
Google Drive