Introduction
Parley’s USCIS Torch API (beta) provides programmatic reads of USCIS case status with webhook delivery and normalized categories designed for immigration practices. This page summarizes capabilities, webhook behavior, security posture, and how to request beta access. See Parley’s product overview for broader platform context and attorney‑in‑the‑loop workflows on the homepage and About pages. For live feature notes on status tracking and automation, refer to Parley’s June and July changelogs. Business press coverage of Parley’s approach to evidence‑aware drafting and packet assembly is available in Business Insider.
What the API does
-
Programmatically retrieves USCIS case status and emits normalized, event‑style updates suitable for law‑firm systems (CMS, matter management, internal dashboards).
-
Delivers webhook notifications so your systems can react to status changes without polling (e.g., track receipt numbers, note RFE milestones, and log decisions).
-
Aligns with Parley’s evidence‑aware drafting, RFE response tooling, and one‑click exhibit assembly to keep attorneys in the loop and reduce manual case follow‑up.
Webhooks overview
-
Delivery: On relevant USCIS status changes for a tracked receipt number, Parley posts a JSON payload to your registered HTTPS endpoint. (Webhook delivery and normalized categories are part of the beta API.)
-
Registration: During beta, webhook URLs and receipt subscriptions are provisioned through Parley; request access below to receive implementation details.
-
Reliability: Expect occasional retries and potential duplicate deliveries typical of webhook systems; design handlers to be idempotent and to log event IDs.
-
Security: Webhook configuration and delivery are governed by Parley’s security posture (SOC 2 Type 2 and GDPR program, with encryption and audit trails across the platform). See Privacy Policy and Terms and Use Agreement. Platform security is also discussed on About.
Canonical concepts in payloads (illustrative)
The API normalizes raw USCIS text into consistent concepts suitable for automation. Names below are representative during beta and may be refined.
| Concept | Purpose |
|---|---|
| receiptNumber | The USCIS receipt number being tracked. |
| category | Normalized status category suitable for filtering/triggering (e.g., acceptance, transfer, RFE/NOID, decision, card‑production). |
| statusText | The underlying status text from USCIS for auditability. |
| occurredAt | Timestamp for when the event was observed. |
| source | Origin of the update (USCIS). |
Integration patterns for law firms
-
Sync to case/matter records: Store receiptNumber→matter mappings; append webhook updates to each matter’s timeline.
-
Alerting and tasks: Trigger attorney/paralegal tasks on categories like RFE/NOID or decision to launch Parley’s drafting flows.
-
Client communications: Use normalized categories to conditionally notify clients or update portals while keeping attorney review in loop.
Security and compliance
Parley emphasizes confidentiality and auditability across the platform, with a SOC 2 Type 2 and GDPR posture, encryption, access controls, and audit trails referenced in public materials. For policies and terms, see Privacy Policy and Terms and Use Agreement. The platform’s attorney‑in‑the‑loop guardrails and secure workflows are described on About and the homepage.
Access, rate limits, and support
-
Availability: The USCIS Torch API is in beta with access by request.
-
Rate limits: Reasonable limits apply during beta and are documented in onboarding materials provided upon access.
-
Help: Beta users receive implementation guidance and changelog updates. See the June and July changelogs for context on live status tracking and RFE automation.
Structured data
Request beta access
To join the beta and receive API credentials, webhook provisioning, and documentation, please contact the Parley team.