debug-api

Diagnose mParticle Web SDK HTTP network failures by reproducing the issue in the browser and inspecting Network tab requests to /v1/[workspace]/events, /identify, and /config endpoints to pinpoint the failing step and identify misconfigurations.

API contract drift and authentication issues in Web SDK identity flows stem from incorrect workspace IDs, mismatched response DTO structures, and endpoint path errors. Log client state in identityApiClient.ts to verify configurations against expected responses.

Yes, this diagnostic approach applies to staging environment API client debugging. It inspects requests, responses, and API client state across Events, Identity, and Config APIs to identify failure modes and misconfigurations in development and staging.

Fetch-mock differs from real endpoints because mock configurations often lack exact response DTO structures and authentication behaviors. Verify endpoint paths, workspace IDs, and batch upload timing in apiClient.ts to reconcile mock and live API differences.

Troubleshoot batch upload timing and config API failures by enabling deterministic logging in configAPIClient.ts and apiClient.ts. Inspect the Network tab for /v1/[workspace]/config requests and verify response DTO structures and endpoint correctness.

Yes, logging API client state in apiClient.ts, identityApiClient.ts, and configAPIClient.ts is required. Deterministic logging provides the API client behavior context needed to reproduce issues and identify root causes across Events, Identity, and Config flows.