Gmf Tech API Customer
Browse all Swaggerhub Gmf Tech APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controloauth227 EndpointsREST
For Agents
Programmatically retornar as configurações completas do cliente | scope-> configuration:read , cria um novo cliente, vinculado à um usuário do sistema. | scope-> configuration. Covers 27 operations with oauth2 authentication.
Use for: I need to retornar as configurações completas do cliente | scope-> configuration:read , I want to cria um novo cliente, vinculado à um usuário do sistema. | scope-> configuration, Search for retornar as configurações básicas do cliente | scope-> configuration:read , Find all atualiza dados do cliente. | scope-> configuration:write
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Swagger da API responsável pela configuração de clientes. The API exposes 27 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the API Customer to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Customer, 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.
1
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 | sh2
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 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.
Capabilities
What an agent can do with API Customer API.
Retornar as configurações completas do cliente | scope-> configuration:read
Cria um novo cliente, vinculado à um usuário do sistema. | scope-> configuration
Atualiza dados do cliente. | scope-> configuration:write
Faz o upload da imagem do cliente (empresa). | scope-> configuration:write
Inclui um novo endereço para o cliente/empresa. | scope-> configuration:write
Use Cases
Patterns agents use API Customer API for, with concrete tasks.
★ Developer Tools Operations
Use the API Customer to perform developer tools operations programmatically. The API provides 27 endpoints covering core functionality including retornar as configurações completas do cliente | scope-> configuration:read , cria um novo cliente, vinculado à um usuário do sistema. | scope-> configuration, retornar as configurações básicas do cliente | scope-> configuration:read .
Call GET /customer/complete to retornar as configurações completas do cliente | scope-> configuration:read
Automated General settings Management
Automate general settings operations by combining multiple API Customer endpoints. Agents can cria um novo cliente, vinculado à um usuário do sistema. | scope-> configuration and then retornar as configurações básicas do cliente | scope-> configuration:read in a single workflow.
Call POST /customer to cria um novo cliente, vinculado à um usuário do sistema. | scope-> configuration, then verify the result
AI Agent Integration via Jentic
AI agents discover and call API Customer 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 oauth2 tokens manually.
Search Jentic for 'retornar as configurações completas do cliente | scope-> configuration:read ', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
27 endpoints — swagger da api responsável pela configuração de clientes.
METHOD
PATH
DESCRIPTION
GET
/customer/complete
Retornar as configurações completas do cliente | scope-> configuration:read
POST
/customer
Cria um novo cliente, vinculado à um usuário do sistema. | scope-> configuration
GET
/customer
Retornar as configurações básicas do cliente | scope-> configuration:read
PUT
/customer
Atualiza dados do cliente. | scope-> configuration:write
PUT
/customer/logo
Faz o upload da imagem do cliente (empresa). | scope-> configuration:write
PUT
/customer/statements
Atualiza as declarações do cliente. | scope-> configuration:write
POST
/customer/address
Inclui um novo endereço para o cliente/empresa. | scope-> configuration:write
GET
/customer/address
Retornar os endereços do cliente/empresa | scope-> configuration:read
GET
/customer/complete
Retornar as configurações completas do cliente | scope-> configuration:read
POST
/customer
Cria um novo cliente, vinculado à um usuário do sistema. | scope-> configuration
GET
/customer
Retornar as configurações básicas do cliente | scope-> configuration:read
PUT
/customer
Atualiza dados do cliente. | scope-> configuration:write
PUT
/customer/logo
Faz o upload da imagem do cliente (empresa). | scope-> configuration:write
PUT
/customer/statements
Atualiza as declarações do cliente. | scope-> configuration:write
POST
/customer/address
Inclui um novo endereço para o cliente/empresa. | scope-> configuration:write
GET
/customer/address
Retornar os endereços do cliente/empresa | scope-> configuration:read
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
API Customer oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'retornar as configurações completas do cliente | scope-> configuration:read ') and Jentic returns the matching API Customer operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct API Customer integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
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
FAQs
Specific to using API Customer API through Jentic.
What authentication does the API Customer use?
The API Customer uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I retornar as configurações completas do cliente | scope-> configuration:read with the API Customer?
Yes. Use the GET /customer/complete endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API Customer?
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 retornar as configurações completas do cliente | scope-> configuration:read through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'retornar as configurações completas do cliente | scope-> configuration:read '. Jentic returns the matching API Customer operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the API Customer have?
The API Customer exposes 27 endpoints covering general settings, addresses, responsible contacts operations.
GET STARTED