Read one shop
The shop's current record, including the stablecoins it can take and whether putty has a recorded address for each. A shop belonging to another user returns the same 404 as one that does not exist.
The shop's current record, including the stablecoins it can take and whether putty has a recorded address for each. A shop belonging to another user returns the same 404 as one that does not exist.
Authorization
bearerAuth A bearer token. The Account routes accept a Privy access token; the MCP transport accepts an sk- API key issued by POST /account/api-keys.
In: header
Path Parameters
The shop's id.
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/business/shops/string"{ "id": "string", "name": "string", "origin": "string", "methods": [ "card" ], "treasuryAddress": "string", "projectId": "string", "stablecoins": [ { "symbol": "usdg", "name": "string", "chain": "string", "chainId": 0, "available": true } ], "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z"}Create a shop POST
Registers a storefront and the ways it will take money. A shop that lists `stablecoin` MUST also send `treasuryAddress`, the shopkeeper's own wallet. putty never holds a shop's takings: the address is handed to the payment provider so the money goes straight from the customer to the shopkeeper. A card-only shop needs no address, because the card processor settles into a connected account on its own. `origin` is the shop's bare host. Every return URL a checkout makes is built from it and checked against it, which is what stops a crafted cart from sending a customer somewhere that is not the shop.
Change a shop PATCH
Updates the fields named in the body and leaves the rest alone. Adding `stablecoin` to `methods` without also sending `treasuryAddress` is refused: a shop that offers to take a stablecoin payment with nowhere to send it is a checkout that takes money and loses it.