Topolo Docs Topolo Platform
Open workspace

List contact people

List the named people attached to a contact, with their role, email, phone, primary flag and archive status.

Outcome

List the named people attached to a contact, with their role, email, phone, primary flag and archive status.

Before you start

  • Verify the intended environment, authenticated identity and specifically approved organization context.
  • The published application permission is contacts:read. Discover the exact granted canonical Books workspace and bind it separately from action input.

Discover the target

topolo whoami --json
topolo actions get app_topolo_books.contacts.people.list --detail --json
topolo resources topolo-books --json
topolo workspaces list topolo-books --json
  • Set BOOKS_WORKSPACE_ID to the exact granted workspace returned by discovery.
  • contactId: Exact contact.id from contacts.list/get; a name or email address is not an id.

Request

GET /api/contacts/{contactId}/people

Inspect and test this action. Save the reviewed input as payload.json; supply credential/resource context separately.

Input fields

FieldRequiredMeaningSchema and constraints
contactIdRequiredExact contact.id from contacts.list/get; a name or email address is not an id.{"type":"string","minLength":1}
includeArchivedOptionalinclude Archived{"type":"boolean"}

Inspect nested fields and the complete input schema.

Effects

  • Reads the selected Books contacts result in the credential-scoped organization and applicable canonical workspace. List the named people attached to a contact, with their role, email, phone, primary flag and archive status.

Interpret the response

Read $.people[].id for the returned contact identifier. Empty collections and nullable fields do not discover a target.

Inspect the actual response fields and retained identifiers for the selected organization/workspace. List the named people attached to a contact, with their role, email, phone, primary flag and archive status. Use the related published read actions when a returned record or ledger outcome needs further inspection; an HTTP 200 does not establish provider delivery or financial agreement.

Inspect the success schema. CLI/MCP add their own transport envelope; CLI --detail requests the full result.

Worked examples

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.

Run a reviewed request

Save the input from the selected worked example as payload.json. Validate and inspect the plan before calling the action; refused examples demonstrate errors and are not instructions to execute.

CLI:

topolo actions validate app_topolo_books.contacts.people.list --data @payload.json --json
topolo actions plan app_topolo_books.contacts.people.list --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_books.contacts.people.list --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --detail --json

MCP tool and arguments for the first successful example:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_books.contacts.people.list",
    "input": {
      "contactId": "con_fd6a873dbd044b81864e7d4abb07e444"
    },
    "resourceType": "workspace",
    "resourceId": "<exact granted workspace id>",
    "detail": true
  }
}

Successful response · HTTP 200

Input · payload.json:

{
  "contactId": "con_fd6a873dbd044b81864e7d4abb07e444"
}

Captured response · HTTP 200

{
  "people": [
    {
      "id": "cps_0c6c894496784b5d8c2e8298a868d140",
      "organization_id": "org_contact-people-route_muvnpzsz4",
      "workspace_id": "ws_contact-people-route_muvnpzsz4",
      "contact_id": "con_fd6a873dbd044b81864e7d4abb07e444",
      "name": "Jordan Lee",
      "job_title": null,
      "email": "jordan@contoso.example",
      "phone": null,
      "is_primary": 1,
      "status": "active",
      "created_at": "2026-10-05T19:42:55.623Z",
      "updated_at": "2026-10-05T19:42:55.623Z"
    }
  ]
}

HTTP 200. Inspect the actual response fields and retained identifiers for the selected organization/workspace. List the named people attached to a contact, with their role, email, phone, primary flag and archive status. Use the related published read actions when a returned record or ledger outcome needs further inspection; an HTTP 200 does not establish provider delivery or financial agreement.

Successful response · HTTP 200

Input · payload.json:

{
  "contactId": "con_fd6a873dbd044b81864e7d4abb07e444"
}

Captured response · HTTP 200

{
  "people": []
}

HTTP 200. Inspect the actual response fields and retained identifiers for the selected organization/workspace. List the named people attached to a contact, with their role, email, phone, primary flag and archive status. Use the related published read actions when a returned record or ledger outcome needs further inspection; an HTTP 200 does not establish provider delivery or financial agreement.

Successful response · HTTP 200

Input · payload.json:

{
  "contactId": "con_fd6a873dbd044b81864e7d4abb07e444",
  "includeArchived": true
}

Captured response · HTTP 200

{
  "people": [
    {
      "id": "cps_0c6c894496784b5d8c2e8298a868d140",
      "organization_id": "org_contact-people-route_muvnpzsz4",
      "workspace_id": "ws_contact-people-route_muvnpzsz4",
      "contact_id": "con_fd6a873dbd044b81864e7d4abb07e444",
      "name": "Jordan Lee",
      "job_title": null,
      "email": "jordan@contoso.example",
      "phone": "+1 206 555 0100",
      "is_primary": 0,
      "status": "archived",
      "created_at": "2026-10-05T19:42:55.623Z",
      "updated_at": "2026-10-05T19:42:55.629Z"
    }
  ]
}

HTTP 200. Inspect the actual response fields and retained identifiers for the selected organization/workspace. List the named people attached to a contact, with their role, email, phone, primary flag and archive status. Use the related published read actions when a returned record or ledger outcome needs further inspection; an HTTP 200 does not establish provider delivery or financial agreement.

Refused response · auth_error

Input · payload.json:

{
  "contactId": "synthetic_books_unresolved"
}

Captured response · HTTP 401

{
  "error": "API key validation failed"
}

HTTP 401. SDK error code auth_error. Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

Verify the result

  • Inspect the actual response fields and retained identifiers for the selected organization/workspace. List the named people attached to a contact, with their role, email, phone, primary flag and archive status.
  • Use the related published read actions when a returned record or ledger outcome needs further inspection; an HTTP 200 does not establish provider delivery or financial agreement.

Errors and recovery

  • auth_error (HTTP 401): Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

These are observed local refusals. Shared authentication, schema validation and resource authorization can also refuse before the route. Preserve the actual error, details and request id.

Recovery boundary

Repeat a read in the same authorized context; no state is changed.

  • List contacts: List customers and suppliers. Filter to one role or include archived contacts, search across name, legal name, email, phone, tax number and city, and sort by name, city, country or when the contact was added.

Evidence

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.