Become a member

01 · Request-reply with named credentials

The synchronous callout, done properly: named credentials for auth, a timeout you chose on purpose, and a mock for the test.

Article 15m 1 min read Updated 15 Nov 2025
01 · Request-reply with named credentials
Modules
Apex Triggers
  1. Module overview
  2. 01 · Order of execution, the map
  3. 02 · One trigger per object
  4. 03 · The handler pattern
  5. 04 · Bulkification: 200 records or bust
  6. 05 · Recursion control
Data Model Basics
  1. Module overview
  2. 01 · Standard objects vs custom objects
  3. 02 · Relationship types, decided with three questions
  4. 03 · Record types and when not to use them
  5. 04 · Schema Builder, the honest map
  6. 05 · Junction objects in practice
Integration Patterns
  1. Module overview
  2. 01 · Request-reply with named credentials
  3. 02 · Fire-and-forget with platform events
  4. 03 · Batch sync without tears
  5. 04 · Middleware or point-to-point?
  6. 05 · Watch: a callout built end to end

The synchronous callout, done properly: named credentials for auth, a timeout you chose on purpose, and a mock for the test.

Named credentials or nothing

Endpoint URLs and secrets do not belong in Apex or custom settings. A named credential moves auth to configuration — and survives the sandbox refresh that would have leaked your token.

Design for the timeout

Every callout needs an answer to 'what if this takes 30 seconds?' If the user is waiting on the answer, the honest fix is usually to make the integration asynchronous.

Practice in your org

  • Open your Developer Edition org and follow along step by step
  • Change one thing at a time and note what happens
  • When something breaks, read the error before searching for it