Skip to main content
A typical seller integration keeps GPU Outlet in sync with an inventory or fleet-management tool. It needs opportunities:read, and opportunities:write for declines. Add introductions:read and introductions:write to follow through after a reveal.
1

Poll for new opportunities

GET /opportunities with opportunities:read lists demand offered to your company. It carries no buyer name, company or ID until you accept:
Response
GET /opportunities/{id} reads a single one. An offered opportunity is waiting for your answer. Without a status filter, the list also includes expired and withdrawn opportunities, which the dashboard does not show on any tab. See Statuses.
2

Decline what you cannot serve

POST /opportunities/{id}/decline with opportunities:write, if the demand does not fit your available capacity:
A key of a trader, an authorized signatory or an owner can decline. A viewer’s key cannot. If the opportunity was already accepted, declined, expired or withdrawn, the call fails with opportunity_not_pending. current in the error carries its actual status.
3

Accept and reveal in the dashboard

Accepting an opportunity reveals the buyer’s company and starts the success fee. The reveal is what commits your company to that fee, so it stays a decision a person makes in the dashboard. Sign in and act on the opportunity there. See Opportunities.
4

Read the introduction after accepting

Once you accept in the dashboard, poll with introductions:read and side=seller:
The introduction now carries the buyer’s legalName, country and buyerContacts. buyerContacts lists the emails and roles of the buyer’s owners and authorized signatories, so you can reach out directly.
5

Confirm you are ready

POST /introductions/{id}/ready with introductions:write:
6

What continues in the dashboard

Invoicing the buyer, confirming the money received and the success fee invoice GPU Outlet issues on it all happen in the dashboard. Sign in to send and track them. See Seller introductions and Success fee.

​
Radar node submissions

The submission endpoints let you propose a whole node for Radar with radar:read and radar:write: GET /radar/submissions, POST /radar/submissions, and the update, withdraw and republish endpoints. They exist only in the partner API. The dashboard has no screen for submitting a node. A submission is not a listing on My Listings. It belongs to the user whose key created it, and it does not appear on My Listings. A listing you publish on My Listings goes on the market at once. A submission is reviewed by the GPU Outlet team before it appears on Radar. On your own submissions, status is pending, approved or rejected, and listed tells you whether buyers can see it right now. Updating a submission sends it back for review.

Buyer workflow

What happens on the other side of the same introduction.

Idempotency

Safe retries for the writes in this workflow.

Errors

opportunity_not_pending, introduction_not_active.

Authentication

Scopes and company context this workflow relies on.