REST and Connect-REST concepts
SUPPLEMENTAL / VERSION-DEPENDENTOriginal learning guide · Pega ’25 path · Content v1.0.0
Learning objectives
- Explain rest and connect-rest concepts in the context of a loan application.
- Identify the configuration decisions and test an expected outcome.
- Recognize a common mistake before it affects users.
Understand the concept
A REST connector defines how the application calls an HTTP service. Understand the endpoint, method, authentication, request schema and response contract. Keep external transport details separate from the business objects that consume the result.
A REST integration exchanges structured requests and responses with another system. A connector defines connection behavior; a data page can present the result to application rules through a consistent interface. Mapping translates external fields into the internal model. Timeouts, authorization errors, malformed responses and empty results require different handling.
Document a simulated credit-check GET or POST contract. Explain the method choice and identify what data must never be placed in logs.
A configuration example
Simulate a credit-rating service with a response containing applicantId, rating and checkedAt. Map the rating into a dedicated result object. Route service failures for follow-up instead of treating them as a negative credit decision.
Application: Loan Origination Case type: Loan Request Learning focus: REST and Connect-REST concepts Given: a known applicant and a documented policy When: the configured step or rule executes Then: compare actual data and routing with the expected outcome
Conceptual configuration plan, not an importable Pega rule. Labels and tools vary by release. Use the official mission environment to inspect current screens.
Try it yourself
Document a simulated credit-check GET or POST contract. Explain the method choice and identify what data must never be placed in logs.
Write sample success, unauthorized and timeout outcomes. Map the successful response. Decide which failures are safe to retry and how a user can continue without exposing credentials or raw service errors.
For this lesson, focus your notes on rest and connect-rest concepts. Record the inputs, configuration choice, observed result and one alternative that you rejected.
Common mistake
Knowledge check
Does an HTTP success response guarantee useful business data?
Check your understanding
No. Validate the response structure and business meaning before using the data.
Go deeper with official resources
Pega Academy System Architect mission
Official ’25 certification objectives
