Bead Developers
  • Introduction
  • Quick Start
  • Authentication
  • Payments
    • Create Payment
    • Payment Statuses
    • Payment Webhooks
    • Test Transactions - Crypto
    • Changelog
  • Entity Management
    • Onboarding
    • Merchant Management
      • Get Merchant
      • Changelog
    • Location Management
      • Create Location
      • Get Location
      • List Locations
      • Update Location
      • Delete Location
      • Changelog
    • Terminal Management
      • Terminal Lifecycle (Concepts)
      • Create Terminal
      • Get Terminal
      • List Terminals
      • Update Terminal
      • Delete Terminal
      • Webhook Management
      • Changelog
  • Settlement
    • Batches
    • Settlement Details
  • Reporting
    • Payment History Concepts
      • Pagination and Sorting
    • Partner Payments
    • Merchant Payments
    • Terminal Payments
    • Changelog
  • Reference Guide
    • Core Concepts
      • Environments & Base URLs
      • Authentication
      • Error Codes
    • Enumerations & Schemas
      • Tender Types
        • Crypto
        • Alternative Payments
      • Settlement Currencies
      • Common Field Types
    • Endpoint Index
      • Table View (All APIs)
      • Download OpenAPI / Postman
    • Payment Scenarios
      • Under- and Over-Payment Handling
      • Reclaiming Unconverted Crypto
    • Operational Guides
      • Compatible Crypto Wallets
      • Webhook Event Reference
    • Support & Contacts
      • Integration Support
      • Escalation Contacts
    • Changelog
  • FAQs & Troubleshooting
    • Authentication FAQs
    • Payments FAQs
      • Resolving “403 Forbidden” When Creating Payments
    • Environment & Testing
      • How to Test Klarna Payments
      • How to Prepare for USDC Testing
      • How to Test Klarna Payments
    • Webhooks & Error Codes
Powered by GitBook
On this page
  • Endpoint
  • Path parameters
  • Request headers
  • Successful response — 200
  • Error responses
  • Best practices for large estates
  • Related endpoints
  1. Entity Management
  2. Location Management

List Locations

Returns all locations that belong to a merchant. The current implementation has no server-side pagination—the entire list is returned in one response.

Endpoint

GET /Merchants/{id}/locations

Path parameters

Name
Type
Required
Description

id

string

✔︎

The merchantId whose locations you want to list

Request headers

Header
Value

Authorization

Bearer <access-token>

Accept

application/json

Example request

curl -X GET "https://api.test.devs.beadpay.io/Merchants/mer_4e5a13aa/locations" \
     -H "Authorization: Bearer $TOKEN"

Successful response — 200

[
  {
    "id": "loc_bfdc6a7f",
    "created": "2025-06-04T16:08:03.226Z",
    "updated": "2025-06-04T16:08:03.226Z",
    "merchantId": "mer_4e5a13aa",
    "name": "Downtown Flagship",
    "tenderTypes": ["ethereum"],
    "maxTransactionAmount": 1000000,
    "address": {
      "address1": "123 Main St",
      "address2": "Suite 200",
      "city": "Springfield",
      "region": "MA",
      "country": "US",
      "postalCode": "01109"
    }
  },
  {
    "id": "loc_c3d1e8fa",
    "created": "2025-06-12T09:15:44.112Z",
    "updated": "2025-06-12T09:15:44.112Z",
    "merchantId": "mer_4e5a13aa",
    "name": "Airport Kiosk",
    "tenderTypes": [],
    "maxTransactionAmount": 0,
    "address": {
      "address1": "987 Terminal Rd",
      "city": "Springfield",
      "region": "MA",
      "country": "US",
      "postalCode": "01109"
    }
  }
]

Each array element is the same object returned by Get Location, minus the nested terminals list.

Error responses

Code
Condition

404

Merchant {id} does not exist or is not visible to your token

Best practices for large estates

✔︎ Action
Why

Cache the result client-side for the session

Avoids fetching the full list on every page change

Filter and paginate in your UI

Server returns everything; handle slicing locally

Request once per minute at most when polling for changes

Reduces bandwidth and keeps within rate limits

Watch for future pagination in the changelog

Endpoint will add cursor or page/size params when merchant estates grow

Related endpoints

  • Create Location – POST /Merchants/{id}/locations

  • Get / Update / Delete Location – manage individual records

  • List Terminals for Location – GET /Locations/{id}/terminals to drill into devices under a store

PreviousGet LocationNextUpdate Location

Last updated 10 days ago