---
title: "Get a Legacy Request's fulfillment"
method: GET
path: "/request-fulfillments/{request_fulfillment_id}"
tags: ["legacyRequests"]
---

# Get a Legacy Request's fulfillment

`GET /request-fulfillments/{request_fulfillment_id}`

## Request

- Base URL: `https://{tenant_name}.benchling.com/api/v2`
- URL: `https://{tenant_name}.benchling.com/api/v2/request-fulfillments/{request_fulfillment_id}`
- Auth: HTTP bearer

Get a Legacy Request's fulfillment

## Path parameters

- `request_fulfillment_id` string, required

## Response `200`

OK

- RequestFulfillment: A Legacy Request fulfillment represents work that is done which changes the status of a request or a sample group within that request. Fulfillments are created when state changes between IN_PROGRESS, COMPLETED, or FAILED statuses. Fulfillments do not capture a PENDING state because all Legacy Requests or Legacy Request Sample Groups are considered PENDING until the first corresponding fulfillment is created.
  - `createdAt` string, date-time: Date and time the Legacy Request Fulfillment was created
  - `entryId` string: ID of the entry this Legacy Request Fulfillment was executed in, if any
  - `id` string: ID of the Legacy Request Fulfillment
  - `modifiedAt` string, date-time: DateTime the Legacy Request Fulfillment was last modified
  - `requestId` string: ID of the Legacy Request this fulfillment fulfills
  - `sampleGroup` SampleGroup: Represents a sample group that is an input to a request. A sample group is a set of samples upon which work in the request should be done.
    - `id` string
    - `samples` SampleGroupSamples
  - `status` 'IN_PROGRESS' | 'COMPLETED' | 'FAILED': Status of a sample group

## Other responses

- `404`: Not Found

---

[API](https://skmtc.dev/benchling/apis/benchling-api-2.md) - [All operations](https://skmtc.dev/benchling/apis/benchling-api-2/llms.txt) - [OpenAPI document](https://skmtc.dev/benchling/apis/benchling-api-2/revisions/01d2fa8523cd?raw)