Gmf Tech API Filter
Browse all Swaggerhub Gmf Tech APIs★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany Dataoauth27 EndpointsREST
For Agents
Programmatically filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:, retornar as configurações de filtragem do cliente (portais, estados e palavras-c. Covers 7 operations with oauth2 authentication.
Use for: I need to filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:, I want to retornar as configurações de filtragem do cliente (portais, estados e palavras-c, Search for filtrar editais coletados, de forma básica, considerando parâmetros de filtragem, Find all incluir/atualizar palavra-chave e termos includentes e excludentes para um clien
Not supported: Does not handle payments, communications, or crm — use for data enrichment only.
Swagger da API responsável pela filtragem de editais. The API exposes 7 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the API Filter to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Filter, 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 Filter API.
Filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:
Retornar as configurações de filtragem do cliente (portais, estados e palavras-c
Incluir/atualizar palavra-chave e termos includentes e excludentes para um clien
Remover palavra-chave e termos includentes e excludentes para um cliente | scope
Simular a filtragem de editais considerando parâmetros de filtragem e textos hip
Use Cases
Patterns agents use API Filter API for, with concrete tasks.
★ Data Enrichment Operations
Use the API Filter to perform data enrichment operations programmatically. The API provides 7 endpoints covering core functionality including filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:, retornar as configurações de filtragem do cliente (portais, estados e palavras-c, filtrar editais coletados, de forma básica, considerando parâmetros de filtragem.
Call POST /filter to filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:
Automated Filtering configurations Management
Automate filtering configurations operations by combining multiple API Filter endpoints. Agents can retornar as configurações de filtragem do cliente (portais, estados e palavras-c and then filtrar editais coletados, de forma básica, considerando parâmetros de filtragem in a single workflow.
Call GET /filter to retornar as configurações de filtragem do cliente (portais, estados e palavras-c, then verify the result
AI Agent Integration via Jentic
AI agents discover and call API Filter 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 'filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
7 endpoints — swagger da api responsável pela filtragem de editais.
METHOD
PATH
DESCRIPTION
POST
/filter
Filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:
GET
/filter
Retornar as configurações de filtragem do cliente (portais, estados e palavras-c
POST
/filter/basic
Filtrar editais coletados, de forma básica, considerando parâmetros de filtragem
PUT
/filter/keyword
Incluir/atualizar palavra-chave e termos includentes e excludentes para um clien
DELETE
/filter/keyword
Remover palavra-chave e termos includentes e excludentes para um cliente | scope
PUT
/filter/global
Incluir/atualizar informações globais de filtro para um cliente | scope-> filte
POST
/filter/simulation
Simular a filtragem de editais considerando parâmetros de filtragem e textos hip
POST
/filter
Filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:
GET
/filter
Retornar as configurações de filtragem do cliente (portais, estados e palavras-c
POST
/filter/basic
Filtrar editais coletados, de forma básica, considerando parâmetros de filtragem
PUT
/filter/keyword
Incluir/atualizar palavra-chave e termos includentes e excludentes para um clien
DELETE
/filter/keyword
Remover palavra-chave e termos includentes e excludentes para um cliente | scope
PUT
/filter/global
Incluir/atualizar informações globais de filtro para um cliente | scope-> filte
POST
/filter/simulation
Simular a filtragem de editais considerando parâmetros de filtragem e textos hip
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
API Filter 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., 'filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:') and Jentic returns the matching API Filter operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct API Filter 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.
FAQs
Specific to using API Filter API through Jentic.
What authentication does the API Filter use?
The API Filter 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 filtrar editais coletados considerando parâmetros de filtragem | scope-> filter: with the API Filter?
Yes. Use the POST /filter endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API Filter?
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 filtrar editais coletados considerando parâmetros de filtragem | scope-> filter: through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:'. Jentic returns the matching API Filter operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the API Filter have?
The API Filter exposes 7 endpoints covering filtering configurations, filtering on-demand, filtering simulation operations.
GET STARTED