ShopEazydevelopers
API referenceMerchant API BetaReference

Address autocomplete (Google Places, South Africa)

Beta
Credentials
  • OAuth access token
Scopes
store:read
GET
/v1/merchant/places

Access: OAuth scope store:read; not write-gated.

Authorization

merchantOAuth store:read
headerAuthorizationBearer <token>

OAuth 2.1 (authorization code + PKCE S256, public clients, dynamic registration) for connected AI apps. Effective power is scopes granted AND the person's role today AND the plan. orders:refund, billing:write and team:write are opt-in on the consent screen. Write implies read for marketing:read and messages:read, so a grant holding marketing:write passes a marketing:read check, and messages:send passes messages:read.

Scope: store:read

Query Parameters

q?string

Fewer than 3 characters returns no suggestions.

Response Body

OK

application/json
  1. response
data*
Example Request
curl -X GET 'https://api.shopeazy.co/v1/merchant/places' \  -H 'Authorization: Bearer <access_token>'
Example Response
{  "data": {    "suggestions": [      {        "id": "string",        "main": "string",        "secondary": "string"      }    ]  }}

The merchant agreement, fee schedule and prohibited uses GET

Public: the route never reads the token today, and the terms are published on shopeazy.co anyway. Access: public, no token; not write-gated.

Resolve a place id into address parts GET

Access: OAuth scope `store:read`; not write-gated.