# Build with Solk > Everything you need to connect Solk CRM to your own software, automation tools, and AI assistants. Solk is a CRM built for B2B sales teams: companies, people, opportunities (sales projects), visits and phone calls, actions, calendar, fair leads, and email threads all live in one place. Each company has its own separate installation that runs at its own address (`https://.solk.app`); the examples in these docs use `https://ornek.solk.app`. The guides on this site show you how to build integrations, move data in and out, and connect the CRM to other tools. The reference sections list every endpoint's parameters, with sample responses taken from a real installation. ## Developer platform :::cards - [REST API](/rest-api/overview) code | Read and write records as JSON. The same endpoints the mobile app uses, with the same permission rules and the same stage gates. - [MCP connector](/mcp/overview) spark | Connect your CRM to AI assistants like Claude: ask questions, and create tasks and log calls right from the chat. - [Webhooks](/guides/webhooks) bolt | Receive signed JSON when an opportunity is won, a new company is created, or a form submission arrives. - [Inbound hooks](/guides/inbound) inbox | Send data into the CRM from forms, your phone system, your data warehouse, and scheduling tools. ::: ## Where to start :::cards - [Quickstart](/quickstart) rocket | Create your first API key and your first task in five minutes. - [Authentication](/rest-api/authentication) key | How API keys, OAuth, and mobile session tokens differ. - [Standard objects](/objects/companies) layers | The fields of companies, people, opportunities, and actions, and how they link together. - [Apps](/guides/apps) grid | Slack, Teams, Zapier, Google Drive, and more than 40 ready-made connections. ::: ## Core principles **One address per installation.** Each customer's data lives in its own server folder and its own database. You send API requests to your installation's address; there is no shared `api.solk.app`. **Runs with user permissions.** Every token belongs to a user. The records the API can see and the changes it can make are exactly what that user can see and do in the web interface: module permissions, record visibility, and edit rights all apply in the API too. **Business rules are never bypassed.** Stage gates when you change an opportunity's stage, duplicate protection when you create a company, the action chain when you log an activity — whatever happens in the web form happens in the API too. Your integration can't break the CRM's rules. **Turkish and English.** These docs are published in two languages. API field names are in English; user-facing error messages (`message`) and some value lists (task priorities, loss reasons) are in the installation's language, Turkish. :::note These docs cover Solk **v22**. To see your installation's version, call `GET /health` or check the `app.version` field of the [identity endpoint](/rest-api/auth/me). Changes are listed in the [changelog](/changelog). ::: ## For AI tools This entire site is also published in a machine-readable form: - [`/llms.txt`](/llms.txt) — a short index of every page - [`/llms-full.txt`](/llms-full.txt) — all content in a single file - [`/openapi.json`](/openapi.json) — the OpenAPI 3.1 definition of the REST API - Append `.md` to any page to get its Markdown version (e.g. [`/quickstart.md`](/quickstart.md)).