---
title: "Get User Fulfillment Info"
method: GET
path: "/orders/{yelp_order_id}/user_info/v3"
tags: ["Checkout API"]
---

# Get User Fulfillment Info

`GET /orders/{yelp_order_id}/user_info/v3`

Get user-provided information for delivery or fulfillment purposes.

This may only be called after the user submitted their billing or fulfillment info on Yelp's checkout page (i.e. Order status needs to be anything but `pending_user_submit`).

This depends on what the Partner specified for the Order's service type.

For example, for Orders of `at_customer` this may be `customer_address` and `phone`.

See [FulfillmentUserInfo](https://docs.developer.yelp.com/docs/resources#fulfillmentuserinfo) for more info.

## Parameters

- `#/paths/~1orders~1%7Byelp_order_id%7D~1update~1v3/put/parameters/0` — unresolved $ref

## Response `200`

Successfully retrieved user fulfillment info.

- object
  - `fulfillment_user_info` object
    - `first_name` string
    - `last_name` string
    - `email` string
    - `phone` string
    - `availability_constraints` Items[] — unresolved $ref

## Other responses

- `403` — This error is returned in any of the following scenarios: | Status | error_code | error_message (example) | ------- | ------------------- | ------------------------------ | 403 | ORDER_STATE_INVALID | Order is in an invalid state to perform this operation. (The Order must be in a state after `pending_user_submit`)

---

[API](https://skmtc.net/yelp/apis/businesses.md) · [All operations](https://skmtc.net/yelp/apis/businesses/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/yelp/businesses/revisions/d3f744f55ed7/schema)