Download the PHP package edos-engineering/reverb-marketplace without Composer

Reverb Marketplace for PHP and Laravel

A client for the Reverb.com marketplace API: listings, orders, shipping, offers, refunds, payouts, messages and webhooks.

This is not Laravel Reverb, the WebSocket server. This package talks to reverb.com, where people buy and sell music gear. Everything here is named reverb-marketplace / ReverbMarketplace, and its environment variables are prefixed REVERB_MARKETPLACE_, so the two can live in one application.

Not affiliated with or endorsed by Reverb.

Requirements

PHP 8.2+. Laravel 12 or 13 for the service provider, facade, webhook route and Artisan command; the client itself also runs without Laravel.

Install

Create the token on Reverb under My Profile → API & Integrations. For a shop integration Reverb recommends the scopes public, read_listings, write_listings, read_orders and write_orders; add read_payouts, read_messages/write_messages, read_offers/write_offers and read_feedback/write_feedback for those resources. Tokens do not expire.

Then check what the application can reach. This writes nothing:

To publish the config file:

Environments

Anything other than the exact word production — unset, a typo — resolves to the sandbox, so a misconfiguration cannot write to a live shop. Tokens are bound to one environment: a production token is refused by the sandbox and the reverse. Sandbox accounts are separate accounts, created at https://sandbox.reverb.com/signup.

One application can address both:

usingEnvironment() and usingToken() return copies; the shared client is never changed.

Usage

Resolve Edos\ReverbMarketplace\ReverbClient from the container, or use the facade. Responses are the decoded HAL+JSON arrays Reverb sent. Collections are a Page (iterable, with total, currentPage, totalPages), and the all… methods return a LazyCollection that fetches pages as it is consumed.

Listings

Reverb's rule for a sync: look the item up by SKU first, update it if it exists, create it only if it does not. Skipping the lookup is how an item ends up listed twice.

Things Reverb's behaviour makes worth knowing:

• A create is a draft unless publish is true. Publishing needs a shop with billing set up and one listing made by hand, and current accounts also need multi-factor authentication; otherwise Reverb answers 403 or keeps the draft. Read the state back with ListingState::fromListing($response).
• Publishing is asynchronous. A create with publish true comes back as a draft with the message "We are processing your request"; Reverb fetches the photos first and emails the seller if the publish fails. Read the listing back before deciding it did not publish; in testing it was live a second later.
• Read warnings. Reverb accepts listings it will not publish and explains only there. A Brand New item needs a valid upc or upc_does_not_apply true; without one it stays a draft indefinitely, with no error and no email.
• A draft cannot be ended (422). A published listing cannot be deleted (400 "Only drafts can be deleted"). end() answers with an empty body.
• An ended listing that never sold comes back with publish true, used conditions included. A used listing that sold is locked for good.
• mine() is a search index and trails a state change by a few seconds; find() is always current.
• Setting inventory to 0 takes a listing off sale: a used listing becomes ended, one that holds inventory becomes sold.
• Only Brand New, B-Stock and Mint (with inventory) can hold more than one unit and relist themselves when stock returns (ListingCondition::supportsInventory()). Any other condition is a one-of-a-kind used item: once it sells, the listing is locked and cannot be relisted.
• "Middle" categories are in the category list but are refused with a 400. List under a leaf category.
• Prefer shipping_profile_id to per-listing shipping.rates. Profiles can only be created on Reverb's website.

Orders

Poll on updated_start_date, not created_start_date: an order placed before the window and paid inside it is otherwise missed. One order is one listing; items bought together share order_bundle_id.

Everything else

Reverb's API is wider than its documentation. Anything not wrapped is still one call away with the same headers, error handling and environment safety:

follow() checks that a link points at a Reverb host and then sends the request to the client's own environment, so a payload can neither leak the token to another host nor steer a sandbox client to production.

Errors

Every failure is an Edos\ReverbMarketplace\Exceptions\ReverbException with status(), errors(), body() and the raw response.

Connection failures and 429s are retried (retries, retry_delay_ms). A 5xx is never retried, and a TransportException on a write is ambiguous: the create may have happened. Look the listing up by SKU before repeating it.

Reverb's limits are 2,000 reads or 600 writes a minute (10,000 / 3,000 per ten minutes). Queue bulk syncs rather than looping.

Webhooks

Reverb's guides do not document webhooks. What this package knows comes from calling the API:

• A registration is a URL and a topic. No headers, no signing secret — deliveries are unsigned.
• orders/paid is the only topic found to be valid for a seller account.
• Registering needs an OAuth token. A personal access token gets 401 "Please log in via Oauth to create webhooks".

Since deliveries are unsigned, the package gates its route with a secret in the URL and refuses everything while none is configured:

Register https://your-app.test/webhooks/reverb-marketplace?token=a-long-random-string and listen:

Reverb retries a delivery that is not answered 2xx, so listeners must be idempotent and slow work belongs on a queue. Keep polling orders()->allSelling() as well: a webhook is the fast path, not the only one. Set webhooks.path to null to skip the route.

Without Laravel

Testing your application

The client uses Laravel's HTTP client, so Http::fake() works as usual:

Developing

The suite never touches the network.

License

MIT.