List social pay orders
/v1/social-pay/orderReturns all social payment orders for the authenticated user, including both sent and received orders with their current status and status history.
Authorization
ApiKeyAuth For accessing these endpoints a valid API key must be sent in the X-Api-Key header.
In: header
Response Body
application/json
application/json
application/json
application/json
application/json
curl --request GET \ --url 'https://gateway.bit2me.com/v1/social-pay/order'[ { "amount": "0.01", "concept": "A concept of pay", "createdAt": "2024-01-01T00:00:00.000Z", "currency": "BTC", "email": "user@example.com", "expiryDate": "2024-01-08T00:00:00.000Z", "note": "A note in the pay", "orderId": "304809b8-0a04-4f88-af75-069ab4e5a36b", "phone": { "countryCode": "34", "number": "666111333" }, "pocketId": "e108f9c3-c3ae-4c43-b2fb-7ac04c2f12f6", "senderName": "Satoshi Nakamoto", "status": "accepted", "statusChanges": [ { "author": "965d26e4-6447-4dc0-a510-72bcca37f510", "created": "2024-01-01T00:00:00.000Z", "newStatus": "waiting-funds", "reason": "Order created" } ], "type": "email", "userId": "cb3795e1-8a1f-47e4-a9ce-d42a1a31785a", "walletMovementId": "965d26e4-6447-4dc0-a510-72bcca37f510" }]Confirm an address book entry POST
Confirms a destination address in the address book without needing the email-based confirmation token. Intended for subaccounts that cannot receive the confirmation email directly. The authenticated user is treated as the address book owner. The operation is idempotent: if the entry is already approved the endpoint returns `204` without error. TOTP is sent via the `x-totp` header; only `gauth` is supported as delivery method.
Claim pending social pay orders POST
Claims one or more pending social payment orders for the authenticated user. Each claim specifies the target pocket where the funds should be deposited. Returns a result per order indicating success or failure with a message.