InstaClaim
    FeaturesPricingAbout
    1. Home
    2. /
    3. Documentation
    4. /
    5. Integrations, API keys, and webhooks

    Integrations

    Use Settings -> Integrations to connect external services and manage developer access for your organization.

    Access

    Integration controls are gated by both plan and role:

    • Connections and Webhooks require an Enterprise subscription and a workspace Admin or Manager role.
    • Tenant API keys require an Enterprise subscription and an Admin role.
    • Creating, renaming, or revoking tenant API keys also requires owner or admin organization membership.
    • Webhook create, update, delete, and test actions allow owner, admin, or manager organization membership.

    If a user lacks the required plan or role, the app shows upgrade or access messaging instead of unlocked controls.

    Connections

    Connections are native integrations used by claim workflows. Accounting providers and redaction services should be connected through backend-held credentials, never through client-exposed secrets.

    Provider setup is being rebuilt from current product evidence and production dashboards. Xero and QuickBooks remain visible as retained accounting providers, but self-serve setup, provider-backed report configuration writes, import jobs, and report generation stay setup-pending until the verified adapters and output fixtures are enabled.

    Tenant API Keys

    Tenant API keys authenticate server-to-server calls to the instaClaim developer API. Create and revoke them under Settings -> Integrations -> API.

    When creating a key:

    1. Choose a clear name.
    2. Select the intended environment.
    3. Add an optional description.
    4. Choose the minimum required scopes, such as claims:read, reports:read, or organization:read.
    5. Copy the full secret from the one-time confirmation dialog and store it in a secret manager.

    Only the prefix is shown after creation. Revoke exposed or unused keys immediately.

    Webhooks

    Webhooks deliver signed events to your endpoint. Use separate endpoints for development, staging, and production where possible.

    Before enabling a production webhook:

    • Verify the destination URL.
    • Store the signing secret in your secret manager.
    • Subscribe only to the events your integration needs.
    • Send a test delivery.
    • Monitor delivery failures and rotate secrets if exposure is suspected.

    Related

    • Account & API keys for account-level API key handling notes.
    • Developer Platform for authentication, SDK setup, MCP tools, webhook contracts, OpenAPI, AsyncAPI, errors, pagination, rate limits, idempotency, and versioning policy.
    InstaClaim
    HomeFeaturesPricingAboutArticlesDocumentationDevelopers
    © instaClaimPrivacy & CookiesTerms