Use your own support interface.

What this path is for

Use the server API when you want Sondel responses inside an interface that you control. The reviewed app source includes a scoped HTTP API and an OpenAPI contract. This is a developer path. It is not a native connector to every service with an API.

Ask Sondel for

The current contract, supported routes, and a test configuration for your tenant and use case.

Keep on your server

The scoped API credential. Do not put a secret credential in a page, browser storage, mobile bundle, or public example.

Keep in your interface

Customer identity, account scope, permission checks, required confirmations, sources, decline states, and the human handoff path.

Verify the full request

• Bind the customer identity and account scope to every request.
• Check the customer has permission before you expose an account fact or action.
• Show the exact change and any charge before the customer confirms it.
• Show the sources and any decline or handoff state returned for the request.
• Handle rate limits, timeouts, and partial failures without reporting success.
• Test revoked credentials, missing permission, failed confirmation, and the actual handoff destination.

Current capability depends on setup. Confirm support before a production launch. Source-level implementation does not promise every route, region, connector, or service level.

Task import is a starting point

The owner area includes an import path for an uploaded OpenAPI specification or a guarded HTTPS specification URL. Importing a declaration does not approve the resulting task, configure its credentials, or prove the remote system's behaviour. Review the operation, identity requirements, amounts, effects, and response confirmation before testing it.