Resources
Reaching every collection by name, and the verbs each one takes.
Every collection in the API has a name here. Names are singular, and the verbs are the same everywhere the API implements them:
pxb customer list
pxb customer get acc_123
pxb customer create -d '{"fullname":"Ada Lovelace"}'
pxb customer update acc_123 -d '{"status":"ACTIVE"}'
pxb product delete prd_1
No collection has all five — the API decides. A resource on its own prints the verbs it really has, the scopes they need, and whether it wants a location pinned:
pxb support-case
pxb help resources prints every collection with its verbs, in one table.
Verbs that aren't CRUD
Where an endpoint does something the five verbs can't say, it keeps its own name. Those that take a single field accept it as a bare argument, so the common call needs no JSON:
pxb support-case message case_1 "Any update on this?"
pxb support-case close case_1
pxb appointment update-status apt_7 CONFIRMED
pxb location archive loc_2
pxb payment-method set-default pm_9
The fallback
The HTTP verbs reach any path, named or not, so an endpoint works the day it ships rather than the day it gets a name:
pxb get customers/acc_123/custom-fields
pxb post departments -d '{"name":"Support"}'
They are the backstop, not the intended route. Needing one for something that has been in the API a while means this table has fallen behind — worth saying so.
In your terminal: pxb help resources