Gmf Tech API Customer

Name: API Customer API
Brand: API Customer
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controloauth227 Endpoints

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.

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

GET STARTED

Start building with API Customer API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

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

Credential isolation

Your API Customer OAuth2 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 'read complete customer configuration' or 'add a customer address', and Jentic returns the matching API Customer 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 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

Can I limit what my agent is allowed to do with the API Customer?

Yes. Because you run Jentic One yourself, your own rules decide which API Customer operations and credentials the agent can use. Since every call acts on the authenticated account and carries its target in the request body, scoping is operations-only: you can allow read operations such as GET /customer/complete or GET /customer/address while leaving out writes like POST /customer or PUT /customer/logo. The agent can only call the operations you have granted, and its OAuth2 credentials are injected at execution time rather than exposed in the prompt.