APIs & Integrations

Use known requests and JSON immediately; introduce service contracts, headers and response validation.

1. Retrieve a Customer From a Service Contract

   Use known GET and a dummy key; read the required header, resource identity and response contract before executing.

   PlannedFree (planned)

2. Inspect Headers and Authentication

   Read content type, API-key and bearer authorization headers while keeping credential values out of logs.

   PlannedFree (planned)

3. Choose the Endpoint for the Job

   Distinguish a collection from one resource and use supplied endpoint documentation.

   PlannedPro (planned)

4. Validate a JSON Response Before Using It

   Check documented fields and types before mapping a known JSON response into downstream work.

   PlannedPro (planned)

5. Create a Linked Resource Across Systems

   Use known POST and returned identifiers to create a linked lead with validated input and response.

   PlannedPro (planned)

6. Repair Your First Broken Request

   Diagnose the wrong endpoint, method or malformed JSON in supplied requests.

   PlannedPro (planned)

Revisit mapping with request bodies, query parameters and safe changes.

1. Ask for the Records You Need

   Use documented query parameters for filtering and compare the returned collections.

   PlannedPro (planned)

2. Map API Output Into a Workflow

   Adapt the service's response names and nested values to a receiving action.

   PlannedPro (planned)

3. Match the Shape the Service Expects

   Compare missing, null and invalid fields against a supplied request contract.

   PlannedPro (planned)

4. Change One Part of a Record

   Use a documented PATCH operation and verify the untouched fields afterward.

   PlannedPro (planned)

5. Remove a Test Record Safely

   Use DELETE on simulated data with explicit identity and human confirmation.

   PlannedPro (planned)

6. Build a Contact Sync

   Retrieve, transform and update contacts across two simulated services.

   PlannedPro (planned)

Deepen authentication with scopes, rotation and an OAuth overview; inspect webhook delivery and verification contracts.

1. Find the Missing Header

   Compare failing and working requests, including content type and authorization headers.

   PlannedPro (planned)

2. Give an Integration Only the Access It Needs

   Distinguish authentication from permission using supplied read and write scopes.

   PlannedPro (planned)

3. Manage Credential Lifecycles

   Rotate a dummy key, then introduce delegated OAuth consent, access-token expiry and refresh at a conceptual level.

   PlannedPro (planned)

4. Receive a Webhook and Start Work

   Inspect a supplied event's payload and route it into a workflow.

   PlannedPro (planned)

5. Check a Webhook Before Trusting It

   Use simulated verification results and schema checks; preview why signatures exist.

   PlannedPro (planned)

6. Repair a Webhook That Creates Two Tickets

   Replay a supplied event and trace duplicate effects through the workflow.

   PlannedPro (planned)

Compose requests and transformations while retaining identity across boundaries.

1. Map the Boundaries Before Connecting Them

   Identify who owns a value and what each system expects to receive.

   PlannedPro (planned)

2. Translate Data Between Services

   Normalize different statuses and nested fields into a shared workflow shape.

   PlannedPro (planned)

3. Connect Three Systems

   Enrich a lead, create its CRM record and prepare a support-team notification.

   PlannedPro (planned)

4. Keep One Identity Across Every System

   Follow service IDs and a shared correlation reference through several runs.

   PlannedPro (planned)

5. Repair a Half-Finished Integration

   The first service succeeded and the second failed; inspect what already exists.

   PlannedPro (planned)

6. Find Records That Fell Out of Sync

   Compare supplied records across systems and account for mismatches.

   PlannedPro (planned)

Deepen reliability with status codes, paging, limits and repeat requests.

1. Distinguish Errors, Timeouts and Unknown Outcomes

   Extend known status codes with 403, 409 and 429, plus network failure and timeouts without a response.

   PlannedPro (planned)

2. Retry Within a Time Budget

   Deepen bounded retries with backoff, jitter and deadlines; stop on invalid input.

   PlannedPro (planned)

3. Work Within a Service's Rate Limit

   Inspect a simulated limit response and pause a controlled batch according to documented retry timing; queue architecture is deferred.

   PlannedPro (planned)

4. Retrieve Every Page Without Losing Records

   Follow page numbers or cursors according to supplied documentation.

   PlannedPro (planned)

5. Create Once When the Response Gets Lost

   A create request may succeed before its reply disappears; inspect safe retry options.

   PlannedPro (planned)

6. Build a Sync That Survives API Failures

   Combine paging, limits and bounded retries across supplied service behavior.

   PlannedPro (planned)

Revisit the whole integration with test evidence, security review and operational limits.

1. Test the Integration Contract

   Use happy-path, empty, malformed and changed responses as supplied fixtures.

   PlannedPro (planned)

2. Keep Test Work Away From Live Data

   Compare simulated environments, scopes and credential storage responsibilities.

   PlannedPro (planned)

3. Repair a Broken Integration

   Diagnose an endpoint change and a shifted response shape from logs and documentation.

   PlannedPro (planned)

4. Build a Real API Integration

   Use realistic simulated service contracts to receive an event, enrich data and update two systems.

   PlannedPro (planned)

5. Run a Failure Drill Before Delivery

   Exercise duplicate events, expired keys, service limits and partial writes on your capstone.

   PlannedPro (planned)

6. Explain the System You Built

   Present the data contracts, operational limits and maintenance plan for an operational handover.

   PlannedPro (planned)