Cases
Cases, participants, progress, documents, relationships, notes, tags and configuration.
UnionStack Developer Platform
Use secure, tenant-aware APIs to connect people, cases, communications and reporting with the tools your teams already use.
OAuth 2.0 · PKCE · tenant-aware
Administrators generate credentials in UnionStack. Authorized users consent to access, and API requests remain scoped to their organization and permissions.
const response = await fetch(
`${baseUrl}/api/Cases/${typeId}`,
{
headers: {
Authorization: `Bearer ${accessToken}`
}
}
);
const cases = await response.json();UnionStack 2.0 API evidence
This example uses the published GET /api/Cases/{typeId}/DataTable operation with its documented minimal response fields. Identifiers and values below are fictional; the operation and field names follow the UnionStack 2.0 controller contract.
GET /api/Cases/11111111-1111-1111-1111-111111111111/DataTable
?minimal=true&active=true
Authorization: Bearer <access-token>
Accept: application/json{
"recordsTotal": 1,
"data": [
{
"caseId": "22222222-2222-2222-2222-222222222222",
"number": 2048,
"name": "Document request",
"createdDatetime": "2026-08-08T15:30:00Z",
"statusId": "33333333-3333-3333-3333-333333333333",
"status": { "name": "In review" },
"typeId": "11111111-1111-1111-1111-111111111111",
"type": { "name": "Grievance" }
}
]
}Run the request with an authorized test user, reconcile the returned count with the same filtered case view in UnionStack, inspect representative records and verify that a user with different permissions receives only the records their role permits.
API coverage
Cases, participants, progress, documents, relationships, notes, tags and configuration.
People, leaders, contact and location records, positions, dues and configurable types.
Organizational structure, agreements, leaders, relationships, sites, documents and announcements.
Email resources and connected Mailchimp audiences and members.
Meetings, types, documents, participants and related cases or entities.
Users, settings, licensing, reporting, domains and authentication.
Developer resources
The public developer site includes an authorization guide, security concepts and the complete grouped OpenAPI reference published by UnionStack WebServices.
Integrations can follow the same connected model as the application. A workflow can start with a person or organizational entity, retrieve related positions or cases, work with case participants and progress, connect meetings or documents, and return useful results without flattening the relationships that give union data meaning.
OAuth 2.0 authorization with PKCE lets users grant access through a documented flow. Tenant-aware APIs keep requests within the authorized organization and permission context, while grouped reference documentation makes it easier to discover related endpoints before implementing production integrations.
Open UnionStack API documentationWorkflow examples
Read: retrieve configured people, positions and entity relationships within the authorized tenant.
Transform: preserve stable identifiers and controlled values rather than flattening names into an ambiguous export.
Validate: reconcile counts and sample members across locals, bargaining units or workplaces before publishing the report.
Read: retrieve the required case types, assignments, participant roles and progress information.
Transform: calculate only the workload measures approved by the organization; avoid exposing case narrative unnecessarily.
Validate: compare dashboard results with sampled cases and test access using a user with representative permissions.
Start: resolve the approved person or entity context and retrieve only the fields required for the service.
Relate: preserve links to positions, cases or meetings when they explain the result.
Operate: document credential rotation, errors, retries, ownership and the authoritative system for every shared value.
Production checklist
Name the system that creates and maintains every shared field. Avoid accidental two-way ownership.
Request only the resources and permissions required for the first useful workflow.
Keep secrets out of browser code and repositories, assign an owner and document rotation and revocation.
Use stable record identifiers and explicit relationship mapping rather than matching people by name.
Design idempotency, retry, alerting, reconciliation and manual recovery before production use.
Reassess users, credentials, data scope and downstream retention when the workflow or vendor changes.
Related implementation guides
Use these maintained UnionStack 2.0 guides to evaluate the workflow in detail.
Use OAuth 2.0 with PKCE and tenant-aware APIs to extend a defined UnionStack workflow.
Support Team · UnionStack 2.012 min read → AccessGive each person the access required for their responsibilities without widening it unnecessarily.
Support Team · UnionStack 2.09 min read → Data qualityKeep records consistent enough to search, connect, report and maintain over time.
Support Team · UnionStack 2.08 min read → ReportingTurn connected records into operational insight while checking definitions and data quality.
Support Team · UnionStack 2.010 min read →Built for connected work
Inspect the public API documentation, then validate one authorized workflow during your trial.