> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# RedCircle API

> Connect DialNexa calls to RedCircle API for vault item, access request, identity check, security review, policy exception, or suspicious-call escalation workflows.

RedCircle API is the real-time Target product data API for accessing Target product catalog, reviews, and category data.

<Note>
  Use RedCircle API with DialNexa when the caller asks for access, recovery, permission changes, vault help, or anything that could expose sensitive systems.
</Note>

## Where RedCircle API fits in a DialNexa workflow

RedCircle API should receive DialNexa output when the conversation affects a vault item, access request, identity check, security review, policy exception, or suspicious-call escalation. The handoff should explain what the caller asked for, what DialNexa learned, which record or object is affected, and who owns the next step.

<CardGroup cols={2}>
  <Card title="Keep secrets out of notes" icon="check-circle">
    Store a safe summary and links to restricted evidence instead of writing passwords, tokens, keys, or recovery codes.
  </Card>

  <Card title="Preserve the audit trail" icon="check-circle">
    Attach call ID, owner, decision, timestamp, and review outcome so security can reconstruct what happened.
  </Card>

  <Card title="Route policy exceptions" icon="check-circle">
    Send unusual access requests to the correct security or IT owner with the policy, reason, and urgency attached.
  </Card>

  <Card title="Verify the caller before access changes" icon="check-circle">
    Capture who called, what access they requested, which workspace is affected, and whether identity confidence is high enough for review.
  </Card>
</CardGroup>

## What DialNexa should capture for RedCircle API

* Caller identity, organization, role, account, phone, and verification confidence
* Requested permission, policy exception, recovery action, affected system, and severity
* Risk reason, suspicious phrases, urgency, approval requirement, and escalation owner
* Safe summary, transcript link, recording link, DialNexa call ID, and review status
* Redaction flag for secrets, tokens, passwords, keys, or recovery codes

## High-value RedCircle API workflows

<AccordionGroup>
  <Accordion title="Security needs a post-call incident note">
    For this scenario, DialNexa should treat RedCircle API as an escalation destination. Send the impact, urgency, affected customer or object, owner, and transcript link so the right team can act before the issue gets colder.
  </Accordion>

  <Accordion title="Caller asks for emergency account recovery">
    For this workflow, DialNexa should send RedCircle API a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
  </Accordion>

  <Accordion title="Employee requests access to a restricted vault">
    DialNexa should keep this people workflow minimal and private: identity, role or case, requested next step, owner, timing, and sensitivity flag. Do not copy unnecessary personal details into RedCircle API.
  </Accordion>

  <Accordion title="Support needs identity confirmation before sharing private details">
    For this workflow, DialNexa should send RedCircle API a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
  </Accordion>

  <Accordion title="A caller mentions leaked credentials or phishing">
    For this workflow, DialNexa should send RedCircle API a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
  </Accordion>

  <Accordion title="Use create collection">
    Use create collection only when DialNexa has a matched caller, a clear destination object, and enough call context to justify opening a new security record. If the caller is unclear, route to review instead of creating noise.
  </Accordion>

  <Accordion title="Use update collection">
    Use update collection when the caller changes a field, status, owner, date, priority, note, consent choice, or next step on an existing RedCircle API record. Include the old value, new value, and reason from the call.
  </Accordion>
</AccordionGroup>

## Workflows that pair RedCircle API with other integrations

* [RedCircle API](/integrations/redcircle_api) + [Gmail](/integrations/gmail): Gmail for approved follow-up after review.
* [RedCircle API](/integrations/redcircle_api) + [Zendesk](/integrations/zendesk): Zendesk for the support ticket that triggered the access request.
* [RedCircle API](/integrations/redcircle_api) + [Slack](/integrations/slack): Slack for urgent review by security or IT.
* [RedCircle API](/integrations/redcircle_api) + [Jira](/integrations/jira): Jira for longer remediation work.
* [RedCircle API](/integrations/redcircle_api) + [Google Docs](/integrations/googledocs): Google Docs for audit notes and incident summaries.
* [RedCircle API](/integrations/redcircle_api) + [Google Sheets](/integrations/googlesheets): Google Sheets for access-review queues.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running RedCircle API actions.
* Write a short operational summary into RedCircle API and link to the full transcript or recording for audit.
* Map required fields before launch: destination object, owner, status, urgency, next step, and record URL.
* Create review paths for low-confidence matches, sensitive requests, high-value customers, and actions that change money, access, legal terms, or customer commitments.

## FAQs

<AccordionGroup>
  <Accordion title="When should a call become a security review?">
    Create a review when the caller asks for account recovery, admin access, permission changes, shared secrets, unusual exceptions, or anything that changes security posture.
  </Accordion>

  <Accordion title="How should identity confidence be handled?">
    Send the verification method, confidence level, failed checks, and reviewer requirement as separate fields so the security team can see why DialNexa did or did not proceed.
  </Accordion>

  <Accordion title="Can DialNexa trigger access changes directly?">
    Only for low-risk, pre-approved flows. Admin rights, emergency access, credential changes, and policy exceptions should require a human approval step.
  </Accordion>

  <Accordion title="What should happen after failed verification?">
    Stop the account-changing workflow, create a restricted review item, and include the attempted request, failed checks, call ID, and escalation owner.
  </Accordion>

  <Accordion title="What belongs in the audit trail?">
    Caller identity, requested action, reviewer, decision, timestamp, policy reason, DialNexa call ID, and links to restricted transcript or recording evidence.
  </Accordion>

  <Accordion title="How should suspicious callers be routed?">
    Tag the risk reason, avoid giving sensitive details, and notify the security or IT channel with the safe summary and evidence links.
  </Accordion>

  <Accordion title="What should stay out of Slack or CRM?">
    Secrets, recovery phrases, private keys, full transcripts, and detailed internal security reasoning should stay in restricted systems.
  </Accordion>
</AccordionGroup>