Ask PCIFIC

Your server sends a customer's question. Ask PCIFIC reads your documents and returns a short answer with sources and optional quotes. You build the question box. Citations always point to a real source Ask has read, and quotes are checked word for word. Ask is instructed to stay within its sources, but a sentence can occasionally add general advice that is not in them.

Ask PCIFIC supports English only; other languages are not supported yet.

What an answer means

• answered: the AI wrote an answer. It is instructed to use your live documents, the item you sent and, only if you allow it, web sources. sources identifies the real sources it read, without guaranteeing support for every sentence. Neutral explanations of general terms may use general knowledge without a source; they do not establish facts about this listing.
• Quote blocks are optional by default. Send quotes: true to request one whenever a document supports the answer. If the AI omits a valid quote, PCIFIC includes the first paragraph of a cited section. quoteAvailable is true when the answer includes a verified quote, otherwise false. No internal quote message is added to the buyer answer. A quote is the document's own words. Before it is sent, PCIFIC checks the words are really in that section of that document. A quote that does not match is removed, and so is any source tag that points at something the AI was not shown.
• The sentences around a quote are the AI's own wording. It can still misread a policy, so show the sources beside the answer, and do not treat an answer as legal or financial advice.
• An answer is only as complete and as current as your documents. A version waiting for approval does not answer yet.
• not_covered: nothing you wrote covered the question. The answer is your fallback message (the standard one until you set your own), supportLink is filled in, and the question goes on your unanswered list so you know what to write next.
• Show aiNotice beside every answer, so people know an AI wrote it. You set the notice in your shop settings.

How you can use it

The same tool works for every row: the documents and the item change, nothing else does. An item can be anything a customer is looking at: a listing, a product, a policy, a property or a booking.

Before you start

• An API key (a secret password your server sends with each request). A test key needs the ask-pcific permission to ask, the documents permission to add documents, and the settings permission to change settings or item lookup. Live keys, test keys and permissions are on the API keys and permissions page.
• At least one live document. Without one, a question is refused with ASK_NO_DOCUMENTS.
• Ask PCIFIC switched on. It is on by default (enabled in the settings).
• A name for your business in the shared shop settings. The AI answers on behalf of that name. Shop configuration also holds the aiNotice you show beside each answer.
• A server of your own that calls PCIFIC. Never put the key in a web page or an app, where anyone could copy it, and never call Ask PCIFIC from the customer's browser.

How it works

Answer and block text contain no citation tags. Each text block has a separate sources list naming the document section, listing or web page it used. Source number starts at 1 for each answer; show that number beside the relevant block. Quote blocks refer to sourceNumber. Internal tag, documentId and itemId are for your server, not buyer-facing labels. The AI is instructed to put your shop documents before seller wording on policy questions and to use supplied sources for facts about the listing, seller, deal and shop. Ask can still explain general concepts neutrally; judgments about a particular seller or deal need to be stated in a document or the listing.

What the AI can use

• Your live documents. It sees a list of their titles and main headings, chooses the ones that fit the question, and opens them in full.
• The item you sent, or one looked up from your own system by its id. Item text is treated as information only: if a seller writes "ignore your instructions" in a listing, the AI does not follow it.
• Web search, only if webSearch is on (it is by default). It is for general facts such as a product's specifications, and the AI is told never to use it for your own policies. One search reads the top 3 pages, and an answer can search at most 2 times.
• Your tone notes, or the shared voice from your shop settings if you set none, as style only. They cannot change what the AI is allowed to say.

Quickstart

These steps use a test key in $PCIFIC_TEST_KEY with the documents, ask-pcific and settings permissions. The ids and times in the answers are examples, yours will differ. These example answers show successful source use; other answers can occasionally include general advice absent from their sources.

Document uploads share a bounded allowance across the API and dashboard: eight uploads and 64 MiB of reserved input per server, with two uploads and 22 MiB per business across all shops and keys. Web-address downloads and refreshes share this allowance; busy background refreshes stay due for the next run. PCIFIC reserves Content-Length before reading; a missing length reserves the full 10 MiB plus 64 KiB request allowance, and real streamed bytes are checked. PDF conversion waits at most two seconds for a reader. A 429 DOCUMENT_UPLOAD_LIMIT means your business is at its share; 503 DOCUMENT_UPLOAD_BUSY means server capacity is full or the PDF wait ended. Both include Retry-After: 20. Try the upload again after 20 seconds. A 408 DOCUMENT_UPLOAD_TIMEOUT means the body did not finish arriving within 20 seconds: check your connection and retry, or split a large file. These limits also cover Word, HTML, Markdown and text files, JSON documents and replacements.

Step 1: add a document

Headings written as # Heading become sections. The answer is 201 (created) and the document is live straight away, because reviewMode is automatic by default.

curl -X POST https://business.pcific.ai/api/v1/documents \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"Returns policy","text":"# Who can return\nYou can return any item within 30 days of delivery.\n\n# Refunds\nRefunds go back to your original payment method within 5 working days of us getting the item."}'

{
  "id": "9c1f5b0e-3d6a-4a52-8f55-2b7d1c0a4e11",
  "title": "Returns policy",
  "source": "text",
  "url": null,
  "fileName": null,
  "status": "live",
  "published": true,
  "liveVersion": {
    "id": "e07a4c19-6b2d-4f38-a1c5-83d9b0f2c764",
    "createdAt": "2026-10-19T09:00:00.512Z",
    "characters": 173,
    "approvedAt": "2026-10-19T09:00:00.512Z",
    "approvedBy": null
  },
  "waitingVersion": null,
  "lastCheck": null,
  "lastChangedAt": null,
  "createdAt": "2026-10-19T09:00:00.512Z",
  "updatedAt": "2026-10-19T09:00:00.512Z",
  "warnings": []
}

You can instead give a web address, which PCIFIC copies now and checks daily, or upload a file. See Documents below. A document added from a web address also lets answers show a page link to it.

Step 2: ask a question

curl -X POST https://business.pcific.ai/api/v1/ask-pcific \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question":"Can I return this coat if I change my mind?","quotes":true,"item":{"type":"listing","title":"Wool coat, navy, size M","details":{"condition":"Used, good","status":"Available"}}}'

{
  "conversationId": "4b0c2d7e-5a3f-4c1e-9b7a-2e8d6f1a0c35",
  "status": "answered",
  "answer": "Yes. You can return it within 30 days of delivery.\n\n\"You can return any item within 30 days of delivery.\"",
  "blocks": [
    {
      "type": "text",
      "text": "Yes. You can return it within 30 days of delivery.",
      "sources": [
        {
          "number": 1,
          "tag": "d1.1",
          "type": "document",
          "documentId": "9c1f5b0e-3d6a-4a52-8f55-2b7d1c0a4e11",
          "document": "Returns policy",
          "section": 1,
          "heading": "Who can return"
        }
      ]
    },
    {
      "type": "quote",
      "text": "You can return any item within 30 days of delivery.",
      "sourceNumber": 1,
      "documentId": "9c1f5b0e-3d6a-4a52-8f55-2b7d1c0a4e11",
      "document": "Returns policy",
      "section": 1,
      "heading": "Who can return"
    }
  ],
  "sources": [
    {
      "number": 1,
      "tag": "d1.1",
      "type": "document",
      "documentId": "9c1f5b0e-3d6a-4a52-8f55-2b7d1c0a4e11",
      "document": "Returns policy",
      "section": 1,
      "heading": "Who can return"
    }
  ],
  "quoteAvailable": true,
  "supportLink": null,
  "aiNotice": "Generated with our company AI. Please verify the information before relying on it.",
  "release": "2.0.0",
  "warnings": []
}

Show the blocks in order: a text block as a paragraph, a quote block as a quote with its document and section, and a page block as a card or button that opens the link. Keep conversationId to carry on the chat.

Step 3: carry on the chat

Send the conversationId from the last answer with the customer's next question. The AI then sees the last 8 turns of the chat. Leave it out to start a new chat.

curl -X POST https://business.pcific.ai/api/v1/ask-pcific \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question":"How long do refunds take?","conversationId":"4b0c2d7e-5a3f-4c1e-9b7a-2e8d6f1a0c35"}'

Step 4: when nothing covers the question

curl -X POST https://business.pcific.ai/api/v1/ask-pcific \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question":"Do you ship to Norway?"}'

{
  "conversationId": "4b0c2d7e-5a3f-4c1e-9b7a-2e8d6f1a0c35",
  "status": "not_covered",
  "answer": "I couldn't find the answer to that in our information. Please contact our support team.",
  "blocks": [
    {
      "type": "text",
      "text": "I couldn't find the answer to that in our information. Please contact our support team.",
      "sources": []
    }
  ],
  "sources": [],
  "quoteAvailable": false,
  "supportLink": "https://example.com/help",
  "aiNotice": "Generated with our company AI. Please verify the information before relying on it.",
  "release": "2.0.0",
  "warnings": []
}

Show the fallback message and offer supportLink. This is not an error: the status is 200. supportLink is null on an answered answer, and it is the support link you set in the settings.

Step 5: read the questions nothing covered

curl -X GET https://business.pcific.ai/api/v1/ask-pcific/unanswered?limit=20 \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY"

{
  "questions": [
    {
      "question": "Do you ship to Norway?",
      "reason": "No document says which countries we deliver to",
      "askedAt": "2026-10-19T09:14:03.221Z"
    }
  ]
}

Newest first. Add a document that covers each one and the next customer gets an answer. An unanswered question is kept for 30 days, and not at all while Ask PCIFIC is on the True ZDR privacy tier (see Monitoring and privacy).

Streaming the answer

curl -N -X POST https://business.pcific.ai/api/v1/ask-pcific \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: text/event-stream" \
  -d '{"question":"Can I return this coat if I change my mind?","quotes":true,"item":{"type":"listing","title":"Wool coat, navy, size M","details":{"condition":"Used, good","status":"Available"}}}'

event: text
data: {"type":"text","text":"Yes. You can return it within 30 days of delivery.","sources":[{"number":1,"tag":"d1.1","type":"document","documentId":"9c1f5b0e-3d6a-4a52-8f55-2b7d1c0a4e11","document":"Returns policy","section":1,"heading":"Who can return"}]}

event: quote
data: {"type":"quote","text":"You can return any item within 30 days of delivery.","sourceNumber":1,"documentId":"9c1f5b0e-3d6a-4a52-8f55-2b7d1c0a4e11","document":"Returns policy","section":1,"heading":"Who can return"}

event: done
data: {"conversationId":"4b0c2d7e-5a3f-4c1e-9b7a-2e8d6f1a0c35","status":"answered","answer":"Yes. You can return it within 30 days of delivery.\n\n\"You can return any item within 30 days of delivery.\"","sources":[{"number":1,"tag":"d1.1","type":"document","documentId":"9c1f5b0e-3d6a-4a52-8f55-2b7d1c0a4e11","document":"Returns policy","section":1,"heading":"Who can return"}],"quoteAvailable":true,"supportLink":null,"aiNotice":"Generated with our company AI. Please verify the information before relying on it.","release":"2.0.0","warnings":[]}

Request fields

POST /api/v1/ask-pcific takes JSON, at most 16 KB. A field it does not know is ignored and named in warnings, so a typo shows up there rather than failing the question.

Send item.details.status with the current availability. Send buyer.accountId for the asking buyer and item.reservedForAccountId for the reservation holder, as opaque account ids, never names or usernames. The backend compares them and only sends the result to the AI: matching ids mean reserved for you; different ids mean unavailable, reserved by another buyer; an explicit null reservedForAccountId means not reserved; otherwise either id missing means ownership cannot be confirmed. An explicit Available or Not reserved status with no reservation holder means not reserved. Neither id reaches the AI. With item lookup, Ask sends buyer.accountId as the buyerAccountId query parameter, including get_item; return status, reservedForAccountId and price at the top level of the lookup JSON. Only price objects with exactly amount and currency use the structured contract. Other shapes, including legacy {value, currency} objects, stay ordinary listing details. If a lookup field is invalid, correct the named field in your configured lookup response and test it again. Never infer reservation ownership from seller wording. Optional item.price uses {amount: 9575, currency: GBP} for £95.75 GBP, the same money format as Orbit and Safeguard. Use a nonnegative whole number in the smallest unit, such as 4500 pence for £45, and a three letter currency code in capitals. Decimal points, exponents and text amounts are refused with 400 ASK_PRICE_INVALID. If you have set up item lookup and send item.id, PCIFIC looks the item up itself and ignores every other item field you sent, so a customer cannot change a price. A warning says so. If you send item.id without item lookup, the request is refused with 400 ASK_ITEM_LOOKUP_NOT_CONFIGURED before AI work. Set up item lookup, or leave item.id out and send the listing details instead.

Response fields

Chats

• Every answer is saved to a chat and returns its conversationId. Send it with the next question and the AI sees the last 8 turns.
• A chat is deleted 30 days after its last question.
• One chat can ask at most 20 questions a minute. A person cannot type that fast, so more means a bot or your code sending a question again and again. The next one gets ASK_CHAT_TOO_FAST until the minute has passed. Other chats are not affected.
• To keep no chats, set keepChats to false. Each question is then answered on its own, conversationId comes back null, and sending one is refused with ASK_CHATS_OFF.

Documents

Add the documents you want Ask PCIFIC to use. An owner or admin can manage them on the dashboard Documents page, or your own system can do it over the API with a key that has the documents permission.

curl -X POST https://business.pcific.ai/api/v1/documents \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com/returns"}'

curl -X POST https://business.pcific.ai/api/v1/documents \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY" \
  -F file=@warranty.docx \
  -F title="Warranty"

What happens to a document

• A web page loses its menus, headers, footers, scripts, forms and buttons, so a cookie banner never becomes the document. A page with no readable text after conversion is refused.
• A Word file keeps its Title and Heading 1 to 6 styles as headings, and list paragraphs become bullets. A Word file's text may unpack to 20 MB at most.
• A PDF becomes plain text and has no real headings, so it is one section unless it is long. A scanned PDF is a picture of text, so it comes out empty and is refused with DOCUMENT_EMPTY: paste its text instead. A PDF that takes too long to read (20 seconds) or too much memory is refused with DOCUMENT_UNREADABLE.
• Text, Markdown and web page files must be UTF-8 (the usual way of saving text). Anything else is refused with DOCUMENT_UNREADABLE.
• Documents are your business's own content, so short text such as "Free delivery." is accepted. Empty documents are refused with DOCUMENT_EMPTY, and binary or damaged text is refused with DOCUMENT_UNREADABLE. A web page file with no HTML tags is refused with DOCUMENT_NOT_HTML: upload the real page, or save the text as .txt. A web page with no readable text after conversion is refused with DOCUMENT_EMPTY.
• Text before the first heading becomes its own section, headed with the document's title. A section longer than 6,000 characters is split again at paragraph breaks into parts that share its heading.
• A web address must be https, have no user name or password in it, and reach a public server (not a private or local one). The check is repeated on each redirect, with at most 5 redirects.

Changes, versions and approval

No API key, test or live, can approve or reject a waiting version. The key sits on your servers, and a leaked one must not be able to put new policy wording in front of customers. POST /api/v1/documents/{id}/versions/{versionId} is for the dashboard only, and an API key that calls it gets 403 DOCUMENT_DECISION_NEEDS_DASHBOARD. Use GET on a document to see its waiting version, and tell an owner or admin to decide.

• A document's status is live (it answers), waiting (only a version waiting for approval, so it answers nothing yet), not_live (its only version was rejected), or unpublished (kept but not used for answers). A version's status is live, waiting, rejected or replaced.
• The live version, a waiting version and the newest 5 versions in all are kept. Older ones are removed.
• Only an owner or admin can change reviewMode on the dashboard Documents page. API keys receive 403 REVIEW_MODE_NEEDS_DASHBOARD when they send this setting.
• Remove on the dashboard stops answers from using the document immediately. Its notice offers Undo for 10 seconds, restoring the same document, tags, versions, approval history and publication state. After 10 seconds removal is final, even if you leave the page. Only owners and admins of your business can undo. Deleting with an API key is permanent immediately and has no Undo.

Text sent as JSON and uploaded UTF-8 text or Markdown is stored exactly as given, including spaces and trailing newlines. Download a version with GET /api/v1/documents/{id}/versions/{versionId} and read markdown to get that same text. Other file formats are converted to Markdown.

Uploaded file names are cleaned before they are stored or returned: folder names, control characters and .. are removed. If nothing remains, PCIFIC uses a document name based on the file's Content-Type.

Document tags and filters

Use optional tags to organise documents, for example returns or shipping. Send tags as a JSON array of up to 5 different lowercase words, each 1 to 24 letters (a to z). With a file upload, send the same JSON array in a part named tags. Tags appear in every document view; documents without tags return [].

Set tags when creating or replacing content. Leaving tags out keeps them on replacement; [] clears them. To edit only tags, send {"tags": ["returns", "shipping"]} to PUT /api/v1/documents/{id}/tags. This keeps the source, text and approval status. On the dashboard, add tags with a document or choose Edit tags, then filter by tag and by live, waiting for approval, unpublished or not live. A document with a waiting replacement appears in both Live and Waiting for approval.

Web page documents

• Daily check. A job runs every hour and checks website documents not checked in the last 24 hours, in batches of 200, five at a time, until all due pages are checked. ETag and Last-Modified stamps let an unchanged site answer 304 without downloading its content. Without usable stamps, PCIFIC downloads the page and compares a content fingerprint before converting or processing it. Unchanged content is never reprocessed. Changed text makes a new version, which follows your review mode.
• Refresh now. Use Refresh now beside a website document on the dashboard, or POST /api/v1/documents/{id}/refresh to check it straight away. Each document allows one manual attempt per minute, including failed attempts. A sooner attempt returns 429 DOCUMENT_REFRESH_TOO_SOON with a next step. The answer's changed says whether a new version was made. Only documents added from a web address can be refreshed.
• lastCheck.at shows when the website was last checked, including an unchanged page or a failed check. lastChangedAt shows when changed text was last saved, including a version waiting for approval. With approve first, the old approved text keeps answering until you approve the waiting update on the dashboard.
• When a read fails, the last good version keeps answering. The failure is saved on the document as lastCheck {at, ok: false, error, tryThis}, and shown on the dashboard.

Settings

GET and PUT /api/v1/ask-pcific/settings. A PUT changes only the fields you send. null clears fallbackMessage and supportLink; voice: null uses your shop voice. A live key can read these but never change them: use a test key with the settings permission, or the dashboard. The full list of every tool's settings is on the Shop configuration page.

curl -X PUT https://business.pcific.ai/api/v1/ask-pcific/settings \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"supportLink":"https://example.com/help"}'

{
  "enabled": true,
  "webSearch": true,
  "reviewMode": "approve_first",
  "fallbackMessage": "I couldn't find the answer to that in our information. Please contact our support team.",
  "supportLink": "https://example.com/help",
  "voice": null,
  "keepChats": true,
  "warnings": []
}

Where the listing comes from

The listing always comes from your own systems, never from the customer's page. Anything on a page can be edited in the customer's browser, so a question box that reads the listing from the page would let anyone get an answer about a price or condition you never set. Set up item lookup once and send only the item's id with each question. PCIFIC reads the listing from your own listings address at the moment the customer asks, so the answer matches what the customer sees, and PCIFIC never stores your listings. Your address answers as it already does, and every field it returns reaches the AI exactly as you named it. If your server sends the item's details with the question instead, read them from your own system at that moment, never from the customer's page.

Item lookup

With item lookup you give PCIFIC an address of yours that answers one item as JSON, and then you send the item id and optional buyer.accountId. The lookup receives buyerAccountId as a query parameter, for example /items/coat-8841?buyerAccountId=opaque-buyer-1. PCIFIC fetches the current details itself, so they are always up to date and the customer cannot change them. The AI can also look up another item by its id when the customer names one.

curl -X PUT https://business.pcific.ai/api/v1/ask-pcific/item-source \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://api.example.com/items/{id}","headerName":"Authorization","headerValue":"Bearer your-items-api-key"}'

{
  "url": "https://api.example.com/items/{id}",
  "headerName": "Authorization"
}

curl -X POST https://business.pcific.ai/api/v1/ask-pcific/item-source/test \
  -H "Authorization: Bearer $PCIFIC_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"id":"coat-8841","buyer":{"accountId":"opaque-buyer-1"}}'

{
  "id": "coat-8841",
  "item": {
    "title": "Wool coat, navy, size M",
    "condition": "Used, good",
    "delivery": "Tracked, 2 to 4 working days",
    "reservation": "cannot confirm who it is reserved for"
  }
}

• url must hold {id} where the item's id goes, and be a public https address. The id is made safe for a web address, and an id of . or .. is refused (ASK_ITEM_ID_NOT_ALLOWED).
• The header is optional. headerName and headerValue go together or not at all. The value is stored encrypted and never shown again. A lookup that carries your header never follows a redirect to a different website.
• A lookup waits at most 5 seconds and reads at most 256 KB. Your address must answer a JSON object, and 404 means the item does not exist.
• PCIFIC fetches the item each time it is asked about, unless your address says its answer stays fresh for a while with a Cache-Control header, such as max-age=300 for five minutes. PCIFIC then reuses that answer until it expires, for at most 48 hours. no-store, no-cache or private means it is fetched every time. An answer for one buyer, with buyerAccountId, is only reused for that same buyer.
• GET /api/v1/ask-pcific/item-source shows the address and header name, never the value. DELETE stops looking items up.
• Item lookup is set up with the settings permission, on a test key.

Errors

Every error is JSON with error (what went wrong), code (a fixed name to branch on), tryThis (the next step) and sometimes problems (the exact fields at fault, as paths). 4xx means fix the request. 5xx means a problem on PCIFIC's side, so wait and try again.

Most errors also have a docs link to their own section on Ask PCIFIC errors, with the usual causes, how to fix it and a request that works. That page starts with the mistakes integrations make most often.

• Ask PCIFIC errors

• Refused straight away: a bad key, a bad body, a switched off tool, no documents, a wrong chat id and every item problem arrive as a normal JSON error with an HTTP status. Nothing is written. This is true when you stream too.
• Failed later: ASK_MODEL_FAILED, ASK_EMPTY_ANSWER and ASK_TIMEOUT happen while the answer is being written. In a JSON request they come back as the response. In a stream the status is already 200, so they arrive as a final error event with the same error, code and tryThis.
• Document, settings and item lookup problems are refused straight away on their own addresses.
• Errors every address can return (UNAUTHORIZED, KEY_NOT_ALLOWED, BODY_TOO_LARGE, RATE_LIMITED, TEST_DAILY_CAP_REACHED, OUT_OF_CREDITS, INVALID_SETTING, BACKEND_UNAVAILABLE and the rest) are on the Errors, limits and retries page. If your business uses its own model, the errors on the Bring Your Own page can also appear.

The unanswered list accepts limit from 1 to 200, default 50. Other values return 400 INVALID_LIMIT. Send a whole number in that range or leave limit out.

Limits

The limits that apply to every address, such as requests a minute, are on the Errors, limits and retries page.

Words used on this page

• Item: whatever the customer is asking about, such as a listing, product, policy, property or booking.
• Document: a piece of your own writing Ask PCIFIC answers from, such as a returns policy.
• Version: one saved state of a document. Every change makes a new one.
• Live and waiting: a live version answers questions. A waiting version is held until an owner or admin approves it.
• Section: a part of a document that starts at a heading. Tags such as d1.2 mean document 1, section 2.
• Source: where a fact came from: a document section, the item or a web page.
• Quote: the document's own words, checked against the document before they are sent.
• Chat: a run of questions with the same conversationId, so a follow-up question makes sense.
• Fallback message: what a customer sees when nothing you wrote covers their question.
• Markdown: plain text where a line starting with # is a heading.
• SSE (server-sent events): a way for a server to send a reply in pieces over one connection.
• https: a web address that starts with https://, the secure kind.

Related guides

• Getting started
• Build it yourself
• API keys and permissions
• Shop configuration
• Errors, limits and retries
• Monitoring and privacy
• Bring Your Own
• Releases