> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/getting-started.md).

# Getting Started

Establish your API, tenant boundary, credentials, and regional endpoint, then validate a first read before building a Concurrence workflow.

For a new Platform project, follow the workspace setup and verified conversation path below. If you maintain an existing Classic integration, choose its separate credential flow in [Choose Credentials](https://docs.concurrence.com/developer-guide/getting-started/credentials.md). Channel provisioning, data connections, and a configured service are additional prerequisites for a working agent interaction.

<figure><img src="https://1651797362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YwM0LHtEGLt9S21OyC3%2Fuploads%2Fgit-blob-9241f2566f609b78de23b6d9da872c2b60582d11%2Fgetting-started-path.svg?alt=media" alt="Choose the API and assigned region, establish tenant and credential access, verify a read, confirm the test service and channel, then run a verified conversation."><figcaption><p>A first project has separate access, configuration, and verification steps.</p></figcaption></figure>

## Build Your First Project

Choose the path that matches your access:

| You have                                                                                                 | Start here                                                                                                                                                                                                                                                                                                                         |
| -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Node.js and npm, with no workspace access yet                                                            | [First Verified Conversation](https://docs.concurrence.com/developer-guide/guides/first-verified-conversation.md), **Local walkthrough**. Run the SDK against fixtures and inspect the result file.                                                                                                                                |
| Test workspace and authoring credentials, without a service                                              | [Create a Test Service](https://docs.concurrence.com/developer-guide/guides/create-a-test-service.md). Create and verify the configuration, then run the conversation starter.                                                                                                                                                     |
| Console access and a configured test service                                                             | [First Console Conversation](https://docs.concurrence.com/developer-guide/guides/first-console-conversation.md). Send a text question, inspect the answer, and end the session in your browser.                                                                                                                                    |
| A configured test service and Platform API credentials                                                   | [First Verified Conversation](https://docs.concurrence.com/developer-guide/guides/first-verified-conversation.md), **Provisioned test service**. Verify an answer in durable history and confirm closure.                                                                                                                          |
| An existing Classic integration                                                                          | [Classic Hello World](https://docs.concurrence.com/developer-guide/classic-api/sdks/sdk-hello-world.md), after you [install](https://docs.concurrence.com/developer-guide/classic-api/sdks/sdk-installation.md) and [configure](https://docs.concurrence.com/developer-guide/classic-api/sdks/sdk-configuration.md) a Classic SDK. |
| Your own backend, an approved SMS sender with an assigned number, and Channel Manager client credentials | [Launch an SMS Outreach Campaign](https://docs.concurrence.com/developer-guide/reference-guides/launch-sms-outreach-campaign.md). Send a controlled message, read delivery status, and test opt-out. This path does not require a Platform workspace.                                                                              |

The prerequisites below apply when connecting to a Platform or Classic deployment. The Channel Manager guide lists its own. The local walkthrough needs no Concurrence account, service, or key.

## Learn by Building

After access is in place, follow the ten-step [Learn by Building](https://docs.concurrence.com/developer-guide/guides.md#implementation-path) path, from a test service to a governed deployment. Each guide ends with a footer that names the next step.

For the mental model behind the steps, read [How a Call Works](https://docs.concurrence.com/platform-overview/how-a-call-works). Classic API credentials are covered in [Classic Authentication](https://docs.concurrence.com/developer-guide/reference-guides/authentication.md) under **Reference Guides**.

## Prerequisites

| Confirm with your implementation team | Platform API                                                                 | Classic API                                                      |
| ------------------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| Tenant boundary                       | Workspace ID for workspace resources                                         | Organization ID and the user represented by the credential       |
| Endpoint                              | Assigned Platform regional hostname                                          | Assigned Classic regional hostname                               |
| Credential                            | Workspace key or the scoped token required by the chosen route               | API key, key ID, and user ID for the token exchange              |
| Workflow configuration                | Service, selected versions, eligible tools, and the required channel binding | Service, selected version set, and the relevant user permissions |

Keep long-lived credentials in your backend or secret manager. Browser and external-user workflows need their documented access boundary. Publishing a workspace key in a client bundle does not create one.

## Essential Reading

1. [Core Concepts](https://docs.concurrence.com/developer-guide/getting-started/core-concepts.md) maps the resource names and boundaries.
2. [Regions & Endpoints](https://docs.concurrence.com/developer-guide/getting-started/regions-and-endpoints.md) explains hostname selection.
3. [Choose Credentials](https://docs.concurrence.com/developer-guide/getting-started/credentials.md) identifies the caller, tenant, and accepted authentication flow.
4. [Govern a Deployment](https://docs.concurrence.com/developer-guide/guides/govern-a-deployment.md) records channel, feature, and regional prerequisites.

## Build Your First Application

For the Platform and Classic paths in [Build Your First Project](#build-your-first-project), complete the corresponding SDK steps below:

* **Platform:** [install the Platform SDK](https://docs.concurrence.com/developer-guide/platform-api/platform-sdk/installation.md), [configure the client](https://docs.concurrence.com/developer-guide/platform-api/platform-sdk/configuration.md) with the assigned workspace and regional hostname, and run the read-only [Quickstart](https://docs.concurrence.com/developer-guide/platform-api/platform-sdk/quickstart.md) before the guides. Then use [Conversations](https://docs.concurrence.com/developer-guide/platform-api/conversations.md) to choose the channel and lifecycle your application needs.
* **Classic:** [install a Classic SDK](https://docs.concurrence.com/developer-guide/classic-api/sdks/sdk-installation.md), [configure the client](https://docs.concurrence.com/developer-guide/classic-api/sdks/sdk-configuration.md) for the correct organization and user, and follow [Hello World](https://docs.concurrence.com/developer-guide/classic-api/sdks/sdk-hello-world.md). Handle stream errors and completion explicitly, then apply the [conversation lifecycle](https://docs.concurrence.com/developer-guide/classic-api/core-api/conversations/conversations-lifecycle.md) for your application.

## Key Resources

A successful authenticated read confirms access to that operation. It does not establish that a channel is provisioned, source data is ready, or a workflow can complete an external action.

Continue with [Guides](https://docs.concurrence.com/developer-guide/guides.md) for implementation paths. Use [Evaluating Concurrence](https://docs.concurrence.com/platform-overview/evaluating-amigo) to define the evidence for a broader technical evaluation, and the [API Reference](https://docs.concurrence.com/api-reference) to inspect operation schemas.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/developer-guide/getting-started.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
