# Connect practice records to your workflow

Keep practice records in step with the software your team uses. The public REST API gives your integration explicit read and write permissions within one selected service line. Every request is checked against the key's current access.

## Wealth: accounts and investment models
Read and maintain account records, investment buckets and investment models. Build an approved sync or reporting workflow around the records your integration may access.

The resource groups are `/v1/accounts`, `/v1/buckets` and `/v1/models`. Read access and write access are separate permissions.

## Tax: filing records
Read and maintain tax-filing records through `/v1/taxfilings`. Connect filing records to your team's preparation and tracking workflow.

These are record operations. For a synthetic individual income-tax calculation, use the [MCP calculation tool](/developers/mcp).

## Commercial Insurance: businesses and policies
Connect business and policy records through `/v1/businesses` and `/v1/policies`. The groups include business people, policy terms, submissions, transactions and renewals.

For example, an integration can read policy terms for a renewal review and record an approved update. You choose the exact operations and permissions during setup.

## Practice records: households, people and activity
Practice records are the shared CRM every profession works from. The resource groups are `/v1/households`, `/v1/contacts` for people, `/v1/touchpoints`, `/v1/tasks` and `/v1/documents`. Use them to keep a household list, contact details, follow-up tasks and documents in step with other business software.

Touchpoints captured from mail, calls, meetings and messages come from the compliance archive, which stays the system of record. The operations your key may call are confirmed during setup.

## Keys that fit the job
Each API key belongs to one organization and one service line. There are three kinds:

- **User keys** belong to a professional and act with that person's access.
- **Agent keys** also name the agent system that uses them, so its activity is easy to trace.
- **Firm keys** support approved organization-level integrations within the selected line.

Requests authenticate with `X-Api-Key`. Keep keys on your server. Each request is checked for current access and the permission the operation needs. Request limits and network restrictions, such as IP allowlists, also apply. Issuing and managing keys requires the matching permission.

## Build against the approved reference
Every approved integration receives the public OpenAPI specification and the `Rutledge.PublicApi.Client` .NET package. Confirm the base URL, version, permitted operations and error responses before connecting live records.

The permission catalog for your service line sets which operations you can use. A website sign-in is separate from API keys.

## A first read-only request
Once our team supplies your approved base URL and a Wealth key with account-read permission, a server-side integration can request one account:

```sh
curl --fail-with-body \
  "$RUTLEDGE_API_BASE/v1/accounts?maxResults=1" \
  --header "X-Api-Key: $RUTLEDGE_API_KEY"
```

Set those variables in your own server environment; this example contains no live address or key. The result is a JSON list of the accounts your key may read. An organization with no accessible accounts receives an empty list, `[]`. Use the OpenAPI model for populated records, identifiers and optional fields. A failed request is not an empty result.

## From question to working connection
1. [Talk with us](/contact) about your integration: name the service line, the task and the exact records you need to read or update.
2. Confirm the base URL, OpenAPI reference, client package and permitted operations with our team. Store the organization key in your server's secret store.
3. Make a read-only request against agreed test records. Check the returned scope and error behavior before adding writes or connecting live records.

## Access and pricing
Bring your service line, workflow, required reads or writes and expected volume. We review API access alongside your seats and confirm usage terms and third-party charges in your agreement.

[Talk with us about API access](/contact) · [Pricing](/pricing) · [Compare MCP tools](/developers/mcp)