Skip to content
UnionStack logo UnionStack

UnionStack Developer Platform

Build the union workflow your organization needs next.

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

Start with secure authorization, then work in context.

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

A versioned case-workload request and response.

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.

Authenticated request

GET /api/Cases/11111111-1111-1111-1111-111111111111/DataTable
    ?minimal=true&active=true
Authorization: Bearer <access-token>
Accept: application/json

Representative 200 response

{
  "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" }
    }
  ]
}
Validation

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

Connected resources, grouped for clarity.

Cases

Cases, participants, progress, documents, relationships, notes, tags and configuration.

People & positions

People, leaders, contact and location records, positions, dues and configurable types.

Entities

Organizational structure, agreements, leaders, relationships, sites, documents and announcements.

Communication

Email resources and connected Mailchimp audiences and members.

Meetings

Meetings, types, documents, participants and related cases or entities.

Platform

Users, settings, licensing, reporting, domains and authentication.

Developer resources

From first token to first workflow.

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 documentation

Workflow examples

Design integrations around an operational outcome.

Membership reporting feed

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.

Case workload dashboard

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.

Connected member service

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

Move from proof of concept to maintained integration.

  1. 01

    Define authority

    Name the system that creates and maintains every shared field. Avoid accidental two-way ownership.

  2. 02

    Choose minimum scope

    Request only the resources and permissions required for the first useful workflow.

  3. 03

    Protect credentials

    Keep secrets out of browser code and repositories, assign an owner and document rotation and revocation.

  4. 04

    Preserve identifiers

    Use stable record identifiers and explicit relationship mapping rather than matching people by name.

  5. 05

    Handle failure

    Design idempotency, retry, alerting, reconciliation and manual recovery before production use.

  6. 06

    Review access

    Reassess users, credentials, data scope and downstream retention when the workflow or vendor changes.

Built for connected work

Build on connected union data.

Inspect the public API documentation, then validate one authorized workflow during your trial.