---
title: "Retrieve Partner's POS Data"
method: GET
path: "/api/v2_1/poses/{posId}"
tags: ["Partner-Merchant-Registration"]
---

# Retrieve Partner's POS Data

`GET /api/v2_1/poses/{posId}`

## Request

- Base URL: `https://secure.payu.com`
- URL: `https://secure.payu.com/api/v2_1/poses/{posId}`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/payu-com/apis/payu-gpo-europe-rest-api/docs/api/v2_1/poses/:posId/get.ts> (a function with typed inputs; its response is checked against the schema)

Retrieve data of the POS with specified `posId`.

## Headers

- `Content-Type` string, required
- `Authorization` string, required

## Response `200`

- object
  - `posId` string: Public POS ID.
  - `type` string: POS type (determines API that can be used).
  - `name` string: POS name.
  - `encoding` string: Determines encoding used by PayU system to read API requests. Always <b>UTF-8</b> for <b>REST</b> type.
  - `authorization` object: Object with authorization details.
    - `standard` object
      - `merchantPosId` string: POS identifier used for API calls. It has the same value as the `client_id` used in the OAuth calls.
      - `key` string: Has the same value as the "`client_secret` used to obtain OAuth access tokens for REST API calls.
      - `secondKey` string: The second API key is utilized for signing notifications sent by PayU, as well as for verifying the notification signature provided by PayU. Additionally, it is used for basic authorization when fetching statement files via the API.
      - `authKey` string: Not required for REST API.

## Other responses

- `401`

---

[API](https://skmtc.dev/payu-com/apis/payu-gpo-europe-rest-api.md) - [All operations](https://skmtc.dev/payu-com/apis/payu-gpo-europe-rest-api/llms.txt) - [OpenAPI document](https://skmtc.dev/payu-com/apis/payu-gpo-europe-rest-api/revisions/185e74d5e007?raw)