# Retrieve Information
source: https://developer.mastercard.com/agent-suite-for-merchants/documentation/use-cases/retrieve-new-database-information/index.md

👉 Replace the generic entities, example endpoints, Mermaid diagrams, and retrieval narratives with the actual lookup flows in your service. Update every Mermaid `basename` to the correct source file in `data/mermaid/`, and replace each Swagger embed with the real OpenAPI file, endpoint path, and method for your retrieve flow. Keep only the record types your API truly exposes.

Retrieve information about a primary resource, secondary resource, transaction record, or administrative record.

### Preconditions {#preconditions}

* The record must already exist in the system.
* Before making a retrieve request, keep the identifier returned by an earlier create or search flow.

## Retrieve Information About a Primary or Secondary Resource {#retrieve-information-about-a-primary-or-secondary-resource}

Use the resource-specific GET endpoint to fetch a previously created record. In the sample specification bundled with this starter, those example endpoints are `GET /dogs/{pet_id}` and `GET /cats/{pet_id}`.

### Example sequence {#example-sequence}

Diagram retrieve-dog-information An operator or downstream system retrieves the full primary-resource profile by its unique identifier. Use the resource-specific retrieval endpoint when you need the complete record before updating, validating, or linking it to a transaction.

See the endpoint structure used by the sample specification:

API Reference: `GET /dogs/{pet_id}`

An operator or downstream system retrieves the full secondary-resource profile by its unique identifier. Use the resource-specific retrieval endpoint when you need a record variant with fields that are not exposed on a general listing endpoint.

See the endpoint structure used by the sample specification:

API Reference: `GET /cats/{pet_id}`

<br />

## Retrieve a Transaction Record {#retrieve-a-transaction-record}

Use the transaction retrieval endpoint to review the current status and payload associated with a downstream business action. In the sample specification, this is represented by `GET /adoptions/{adoption_id}`.

### Example sequence {#example-sequence-1}

Diagram retrieve-an-adoption-record

### Retrieve transaction request {#retrieve-transaction-request}

An operator reviews the status and details of a specific transaction record. Retrieve by identifier when you need to confirm whether the transaction progressed as expected or before applying an update.

See the endpoint structure used by the sample specification:


API Reference: `GET /adoptions/{adoption_id}`

<br />

<br />

## Retrieve an Administrative Record {#retrieve-an-administrative-record}

Use the administrative retrieval endpoint to fetch a specific operational record by its unique key. In the sample specification, this is represented by `GET /employees/{username}`.

### Example sequence {#example-sequence-2}

Diagram retrieve-employee-information

### Retrieve administrative record request {#retrieve-administrative-record-request}

An administrator or manager retrieves a specific operational profile using its stable unique identifier. This is useful before updating account data, reviewing permissions, or confirming current enrollment details.

See the endpoint structure used by the sample specification:


API Reference: `GET /employees/{username}`

<br />

## Error Resolution {#error-resolution}

For details on error resolution please visit our [Code and Formats](https://developer.mastercard.com/agent-suite-for-merchants/documentation/code-and-formats/index.md) section.