Recipes

Focused patterns for common integration tasks. Each recipe is deliberately small: one job, the key API surface, and the implementation notes that matter when wiring a real system.

When to use a recipe

Reach for a recipe when you want a working pattern for a specific task. If you need the complete endpoint list, request and response schemas, or error formats, use the REST API reference instead. If you are designing a larger integration, start with Scenarios to map the workflow before choosing individual recipes.

Setup

Setting up HttpClient

Configure a reusable .NET HttpClient for authenticated Efimis REST API calls.

Clients & matters

Creating a client

Create an entity first, then assign the client role to that entity.

Creating a matter

Open a matter from an existing client and leave firm-specific setup to authorised users.

Time & billing

Posting a work item

Create time entries and disbursements against a matter.

Post a journal entry

Record general ledger postings from an external finance workflow.

Reissue an invoice

Void and reissue an existing invoice without losing the audit trail.

Apply credit notes

Create and apply a credit note against an outstanding invoice.

Ledger & trust

Reconcile a trust account

Query trust ledger activity and verify balances against a statement.

Bulk-import opening balances

Import opening balances in bulk via the ETL pipeline.

Events & webhooks

Subscribing to general ledger postings

Push ledger posting events to an external accounting or reporting system.

Subscribing to invoice issued events

Receive a webhook when an invoice is issued in Efimis.

Querying & reporting

Query for invoice list

Find invoices and inspect their line items through the API.

Query profit and loss data

Use GraphQL to retrieve profit and loss reporting data.

Generate a WIP report

Pull work-in-progress data for a billing period using GraphQL.