API Integration and Enterprise Automation

Define request, response and error schemas for a mock CRM.

Evidence: Consumer tests fail on a deliberate breaking change.

Use safe reads, writes and status codes appropriately.

Evidence: Tests distinguish validation errors from retryable failures.

Compare API keys and delegated tokens; use a secret store.

Evidence: No credential appears in source code, screenshots or logs.

Enforce role and tenant restrictions in service handlers.

Evidence: A user cannot access another tenant by changing an object ID.

Validate event authenticity and deduplicate replayed deliveries.

Evidence: Repeated valid events have one effect; invalid signatures are rejected.

Use a queue with bounded retries and a dead-letter path.

Evidence: A poison message is isolated while later messages continue.

Translate fields and enumerations between two schemas.

Evidence: Unknown values are quarantined rather than silently mapped.

Handle a partial multi-service update with a recovery action.

Evidence: A simulated failure returns systems to a documented consistent state.

Throttle calls and respect retry delays.

Evidence: A burst remains within the declared mock-service limits.

Introduce a new field without breaking existing clients.

Evidence: Both supported contract versions pass tests during migration.

Track failure rates, queue age and correlation IDs.

Evidence: A trace connects one business event across all services.

Document dependencies, ownership and manual recovery.

Evidence: An operator resolves a seeded integration incident from the runbook.