INTEGRATIONS

Your support agent, through an API.

Bring requests in, prepare a change, and approve it with a separate permission.

Two credentials, two responsibilities

Set distinct RESOLVE_API_KEY and RESOLVE_REVIEWER_KEY values of at least 32 characters on the backend. Send the appropriate key in the Authorization: Bearer header. Keep both keys on your server. The API stays disabled until both are configured.

Local API address

http://127.0.0.1:8788/api/v1/agent

Prepare, confirm, approve, verify

Send a typed action with a unique idempotency key and a verification token from your customer verification flow. Review the returned checks and exact plan. Where required, confirm the customer’s choice, then use the reviewer credential to execute the same planHash. Reconcile an unknown outcome; do not repeat a write.

Endpoints

POST · /messages: Create a support request for automatic preparation
POST · /requests: Verify evidence and prepare a concrete action
POST · /requests/{id}/confirm: Record verified customer confirmation
POST · /requests/{id}/execute: Approve and execute with reviewer credentials
POST · /requests/{id}/reconcile: Read back an uncertain operation outcome
GET · /requests/{id}: Read the action state and confirmation reference
GET · /schema: Download the OpenAPI 3.1 description

Connect your own services

The six actions work against fictional demonstration records. To change real orders, appointments or accounts, configure the company service connector and implement its prepare, confirm, execute and operation-status endpoints. The connector must verify ownership, apply policy, recheck state and return authoritative receipts. Privacy requests create reviewed cases; they do not automatically export or erase data.

Mention Resolve in Slack

Install your Slack app in an approved workspace and channel, then mention @Resolve with the customer’s issue. It arrives in the inbox with a summary and a suggested workflow. Add #human-only to avoid external AI. A mention cannot establish ownership or approve an action.

Before publishing an endpoint

This is a single-workspace API. Keep the local operator routes private. A production gateway must expose only the authenticated agent routes over HTTPS, with rate limits, access logging and managed secrets. Multi-company deployment still requires account authentication and company isolation.