The whole integration in order: keys, listing fields, settings, when to call each tool, testing and going live.
You do not need a coding agent to integrate PCIFIC. Every tool is a web address your server calls with a key in the Authorization header. This page is the whole path in order. Each tool has its own page with its fields, errors and examples.
Build and test with a test key: it runs the real tools and spends no credits. A live key is for production and spends credits. Choose Live key and press Activate live key on the API keys page. A live key can read settings and listing fields but never change them, so a leaked production key cannot change how your account is set up. The full list of permissions is on the API keys and permissions page.
Call a tool at the moment its answer changes what the person sees or does, and no more often.
| Tool | Call it when | Don't call it when |
|---|---|---|
| Safeguard listing check | Once, when the seller presses Publish, to review the listing before it goes live. Once when a buyer asks for a check, if you offer that. A review takes a few seconds to a minute, so start it and read it back until it is done. | On every edit or page load, or again for a listing that has not changed since the last result. Reuse the last result until the listing changes. |
| Orbit listing generation | When a seller asks for a draft from their notes and photos. If Orbit asks the seller questions, show them all together and send every answer in one request. | On every keystroke, or to fill in a listing that is already complete. |
| Ask PCIFIC | When a buyer or visitor types a question that your documents could answer. | To prefill a chat box, on page load, or for a question your page already answers in fixed text. |
| PCIFIC PixelTrace | When a seller takes photos in the managed camera, and before publishing to check them. | On every page load, or for listings that have no photos. |
Read code and tryThis before handling a 5xx. A 5xx is on PCIFIC's side: keep building with saved responses, retry after the Retry-After header when there is one, then back off (2, 4 then 8 seconds) and stop after three tries, sending the same Idempotency-Key each time where the call takes one. BYO_PROVIDER_ERROR means your own model provider (Bring Your Own) did not answer: check with that provider that the key, its credits and the model work, and contact PCIFIC support to change them. Never retry a 4xx other than 429 without changing the request. A PCIFIC outage never has to stop a seller saving or publishing.
PCIFIC writes a price as a whole number in the smallest unit of its currency (pence or cents), with the currency code beside it, the way payment systems do. In your listing fields a price field is marked "x-pcific-money": true and is an object like {"amount": 5500, "currency": "GBP"}, which is £55. Send the amount as a number without a decimal point or exponent, not as text: decimal and text amounts are refused. For example, 4500 pence is £45. Your business has one currency, the currency setting in the Orbit settings (GBP unless you change it), and prices are never converted from another currency.
Every error is a JSON body with error, code, tryThis and sometimes problems. Branch on code, and follow tryThis. The shared errors, the limits and the rules for sending a request again safely are on the Errors, limits and retries page.
curl -X POST https://business.pcific.ai/api/v1/listings \
-H "Authorization: Bearer $PCIFIC_TEST_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 4f1c2b9e-7d3a-4c55-9a51-0e6b2f8d1c47" \
-d '{"notes":"iPhone 13 128GB, unlocked, good condition"}'https://business.pcific.ai/openapi.json describes every address the API answers, in OpenAPI 3.1 (a standard file format for describing web APIs). Each address names the test key permission it needs, its errors, the 429 RATE_LIMITED answer with its Retry-After header, and the Idempotency-Key header where the call takes one. Import it into Postman or Insomnia, or generate a typed client from it.