Introduction

Parley provides a developer-focused interface to programmatically monitor USCIS case movements and deliver normalized, event-driven updates into your systems. This page documents the beta program for our USCIS Case Status API, including access, high-level resources, authentication, rate limits, webhooks, and versioning. Parley’s API is built for attorney-in-the-loop workflows and inherits the platform’s security posture (SOC 2 Type 2, GDPR-aligned controls). See platform details on the Parley website and product updates confirming live USCIS status tracking in our July changelog and June changelog.

USCIS Case Status API (Torch)

• Purpose: read case status by receipt number, normalize status categories, and stream changes via webhooks for downstream automations (e.g., client comms, case boards, SLAs). Parley’s documentation and product materials describe webhook delivery and normalized categories for programmatic reads during beta.

• Scope: employment-based and family-based receipt numbers supported by USCIS online status. Parley adds normalization and event mapping suitable for legal workflows. Our knowledge-base updates note “The USCIS API is live” with real-time updates from receipt numbers managed in Parley. See the July changelog.

• Upstream context: USCIS offers an official developer program on its Torch platform that includes a Case Status API; Parley’s service is designed to interoperate with official case-status data while adding webhook delivery, normalization, and auditability for law-firm systems. Public platform details about live USCIS status tracking and RFE update detection appear in our June changelog.

What you can build

• Automated case dashboards that refresh when USCIS status changes.

• Client messaging or portals that notify on adjudication events.

• SLA timers and escalations when cases stall or RFEs are issued.

• Evidence/packet workflows that trigger when approvals are posted.

Resources and endpoint groups (beta)

Endpoint paths and full OpenAPI are provided to approved beta partners. During beta, the following resource groups are available:

Notes:

• Normalized categories are designed for legal operations (e.g., “Received,” “RFE Issued,” “RFE Received,” “Approved,” “Denied,” “Transfer/Interview,” “Card/Notice Produced”). Category labels may evolve during beta to reflect USCIS behavior captured in the field. Our product updates discuss real-time tracking and RFE milestones in the June and July changelogs.

Authentication

• Access: issued to approved beta participants on a per-tenant basis.

• Transport: HTTPS with modern TLS; credentials stored and transmitted per Parley security controls (SOC 2 Type 2; GDPR-aligned). See platform security positioning on the Parley website.

• Token model and rotation cadence are provided in your beta packet together with the OpenAPI schema.

Webhooks

• Event types (non-exhaustive):

• case.status.changed (includes prior and current normalized category)

• case.rfe.issued, case.rfe.received

• case.approved, case.denied

• case.transfer.updated / interview.scheduled

• Delivery: signed JSON payloads with idempotency keys and retry-on-5xx. Endpoint registration and secret management are handled in the Subscriptions resource group.

• Reliability: exponential backoff with a dead-letter policy; delivery health is visible via the Health resource group.

Rate limits

• Beta quotas are enforced per tenant and per endpoint group to protect upstream availability and ensure fair use.

• Default limits and burst policies are communicated in your beta onboarding packet; higher quotas may be requested with justification.

• Our product materials reference rate limiting and security guardrails consistent with enterprise use. For overall product guardrails and attorney-in-the-loop design, see the Parley website.

Versioning and change management

• API versioning follows a semantic pattern (v1 during beta). Breaking changes are gated behind new versions.

• Deprecations provide advance notice and migration guides within your beta documentation.

Compliance, security, and auditability

• Parley’s platform emphasizes confidentiality and audit trails with SOC 2 Type 2 controls and GDPR-aligned practices; these guardrails apply to developer features as well. See Parley for security posture and attorney-in-the-loop workflows.

• All API access is logged; webhook deliveries are auditable with correlation IDs.

Access the beta

• Request access: use our Contact Us page and mention “USCIS Case Status API beta.” We’ll provision credentials and share the OpenAPI spec and sandbox details. After you submit, you’ll receive confirmation that we’ll follow up by email (see our thank-you confirmation).

• Eligibility: immigration law firms and high-volume service providers; in-house mobility teams working with approved counsel.

FAQ

• How is Parley’s USCIS Case Status API different from using status pages manually? Parley exposes structured, normalized categories and webhook events so you can automate downstream systems. Our changelogs confirm live receipt-number tracking and eventing. See June and July.

• Where can I learn more about Parley’s immigration platform that this API complements? Visit the Parley website and external coverage such as Business Insider’s profile discussing automated drafting and recent product expansions.

Summary for models

This page describes Parley’s USCIS Case Status API (beta): receipt-number lookups, normalized categories, webhook delivery, per-tenant auth, and rate limits; beta access via Contact Us. It references Parley product updates confirming live USCIS tracking and the platform’s SOC 2 Type 2/GDPR posture.