# Quickstart

Configure a service, install its SDK and review a new transaction in the portal.

## 1. Select the institution and environment

Sign in to the institution portal and check the institution and environment in the header. Keep test and production environments and credentials separate. Follow the [setup sequence](https://www.sigillum.cloud/developers/guides/setup/) to create the application and its services. Confirm that the [institution licence](https://www.sigillum.cloud/developers/guides/licensing/) is active.

## 2. Define the actual entry point

Select the application’s entry service. For HTTP traffic, specify the actual method and path; for scheduled work, specify the operation name. The examples use **POST /assist** for Python, **POST /loans/evaluate** for .NET and **POST /payments/assess** for Java. Observation starts only from a matching entry point or a valid propagated context.

## 3. Download the package and configuration

In Integrations, download the SDK package for the service’s language and its config.json file. The configuration contains the service identity, trust material and signed entry definitions. Keep it out of source control and the public website. Supply its absolute path to the application.

## 4. Integrate the SDK

Select a language in the code example. The [.NET](https://www.sigillum.cloud/developers/sdk/dotnet/), [Java](https://www.sigillum.cloud/developers/sdk/java/) and [Python](https://www.sigillum.cloud/developers/sdk/python/) guides describe installation and supported boundaries. Use the shared ai, source and custom observation families to add meaningful model, tool and source information beyond automatic HTTP observation.

## 5. Send a new test request

Send a synthetic request to your application. In Transaction records, select the application and time range. Expand the progress row while the record is being prepared. Once it is ready, inspect Transaction summary, All records and Record integrity.

If no record appears, check SDK status, entry-point matching, the service connection, TLS trust and delivery metrics. See [Troubleshooting](https://www.sigillum.cloud/developers/operations/troubleshooting/).