> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Server integrations

> Prepare server-side API access, resource identity, request handling, and deployment verification.

A server integration can use permitted public API operations to manage configuration and inspect stored resources. Runtime sessions and provider execution have their own release requirements.

## Set up the boundary

<Steps>
  <Step title="Scope credentials">Create a key for the intended service and workspace. Follow [API keys](/overview/administration/workspaces/api-keys) and the [authentication reference](/api-reference/authentication).</Step>
  <Step title="Identify resources">Retain agent, branch, version, document, and connection identifiers. Resolve access independently of user-submitted display names.</Step>
  <Step title="Handle responses">Set timeouts, check status, and retain safe request-ID context. Distinguish rejected requests from uncertain mutation outcomes before retrying.</Step>
  <Step title="Read results back">Inspect the stored resource and exact version after changes. Do not infer success from a return URL or local editor state.</Step>
</Steps>

Use [Python](/agents-platform/resources/sdks/python) and [TypeScript](/agents-platform/resources/sdks/typescript) resource pages for checked read examples. The private dashboard session is not an alternative public SDK credential.

## Operational review

Separate development, staging, and production credentials and resource identifiers. Define request limits, access logging, dependency failure behavior, and revocation. Keep secrets and unnecessary customer content out of logs.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does API access include every dashboard operation?" id="faq-server-public-api">No. Use the public contract and the operation's allowed credential type. Internal-web workflows are a separate boundary.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.