Scopes and permissions
Access is limited by company and feature and reassessed based on the responsible user's membership.
INTEGRATIONS / CONNECT YOUR OPERATIONS
Agimpe's intelligence.
In your systems' workflow.
Query data through the API, receive matches through webhooks and connect assistants via MCP. Manage each connection in your company workspace.
Integration API
Query information and update your operational profile with company-scoped and permission-based access.
Match webhooks
Connect relevant events to your operations, with signatures and delivery history.
01 / REST API
One key.
Your company's context.
Create credentials in Integrations, choose scopes and set an expiration date. Each key belongs to a company and respects the responsible user's current permissions.
- Company, monitoring and relevant matches
- Publications related to your company's matches
- View and update your operational profile
- Expiration, revocation and request history
First request
curl 'https://api.agimpe.com.br/api/integrations/v1/company' -H 'Authorization: Bearer YOUR_KEY'GET /companyGET /monitoringGET /matchesGET / PUT /operation-profile
Keys for use on your application's server.
02 / WEBHOOK EVENTS
When a match arrives,
your system knows.
Register an HTTPS URL to receive match.created when a relevant match is created for your company. Test the connection and track every attempt in the dashboard.
- HMAC signature following Standard Webhooks
- Test event clearly marked as fictional
- Up to eight automatic attempts per cycle
- History, manual retries and secret rotation
Event delivery Example
EVENT
match.created Relevant match Your system
Signature verified HTTP 2xx response Delivery recorded
Your system validates the signature and handles duplicates using the event identifier.
CONTROL IN EVERY CONNECTION
Integration also
means governance.
Authorization, request identification and traceability are part of the experience.
Usage visibility
Review last key usage, calls and HTTP history for authenticated requests.
Credential lifecycle
Create a replacement key before revoking the previous one. For webhooks, transition between secrets.
MCP: context for your assistants.
Agimpe’s MCP server connects your assistants to six query tools through Streamable HTTP and Bearer authentication. Create a key with mcp.read and your chosen scopes in Integrations.