Managers — Proposed Guide

Planned API — Reference Only

Managers: A manager relationship would support organizational routing, subject to policy and conflict rules. The relationship is not by itself permission…

Overview

A manager relationship would support organizational routing, subject to policy and conflict rules. The relationship is not by itself permission to approve every expense for that employee.

Key concepts

Check organization boundaries and reject circular reporting relationships. Effective dates may differ from when an update is received.

Implementation considerations

Preserve the manager used by a prior approval rather than rewriting audit history after a reporting-line change.

Proposed API behavior

PATCH /v1/users/{user_id}/manager is an illustrative design for this topic. Path and field names may change before implementation. Access would require an authorized organization context and operation-specific permission; no public API or authorization grant is available here.

Proposed path parameters
Name	Type	Description
user_idrequired	string	Stable fictional user reference; not a secret and not evidence that a resource exists.

Illustrative request fields
Name	Type	Description
manager_id	string	Stable fictional manager reference; not a secret and not evidence that a resource exists.
effective_on	string (date)	Synthetic calendar date in YYYY-MM-DD form; period inclusivity must be defined by the future contract.
version	integer	Illustrative resource revision for detecting stale updates; no live concurrency contract is published.

Static example requests

Proposed, non-executing request examples

# Proposed request text only; this reserved host is not a live API.
curl -X PATCH 'https://api.remizen.example/v1/users/usr_example_123/manager' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  --data '{
  "manager_id": "usr_example_123",
  "effective_on": "2026-01-15",
  "version": 1
}'

Fictional response example

200 (proposed example)Static response fixture

Fictional documentation data only. No request was sent, record created, review performed, payment initiated or provider connection activated.

JSON

{
  "data": {
    "manager_id": "usr_example_123",
    "effective_on": "2026-01-15",
    "version": 1,
    "id": "usr_example_123",
    "organization_id": "org_example_123",
    "display_name": "Taylor Example",
    "email": "taylor@example.com",
    "status": "active"
  },
  "meta": {
    "request_id": "req_example_123",
    "reference_only": true
  }
}

Illustrative error case

Review this failure case in context: Preserve the manager used by a prior approval rather than rewriting audit history after a reporting-line change.

422 (illustrative; final error contracts are undecided)Proposed error fixture

Synthetic diagnostic example. Human-readable messages must not be used as stable programmatic contracts.

JSON

{
  "error": {
    "code": "validation_error",
    "message": "The proposed managers operation requires review of its input or authorization.",
    "request_id": "req_example_123"
  }
}

Proposed data types

Illustrative field dictionary
Name	Type	Description
user_id	string	Stable fictional user reference; not a secret and not evidence that a resource exists.
manager_id	string	Stable fictional manager reference; not a secret and not evidence that a resource exists.
effective_on	string (date)	Synthetic calendar date in YYYY-MM-DD form; period inclusivity must be defined by the future contract.
version	integer	Illustrative resource revision for detecting stale updates; no live concurrency contract is published.

Job Titles

Users & Organizations

Organization Structure