Send pdc-request-source: ai-assisted on POST /orders (Place Order) when an AI assistant wrote or generated your integration. Leave the header out for a standard integration. Print.com uses pdc-request-source to group orders by source in its usage reporting and to help support teams to pin point issues faster.
key facts
- pdc-request-source is an optional header on POST /orders. An order is placed with or without it.
- Print.com uses pdc-request-source to group orders by source in its usage reporting.
- An empty pdc-request-source marks a standard API integration.
- An integration whose code an AI assistant wrote or generated sends pdc-request-source: ai-assisted.
- Use exactly ai-assisted: lowercase, with a hyphen, no spaces. Never invent another value.
Which value to send
| Your integration | pdc-request-source |
|---|---|
| Standard integration, written by your own developers | Leave the header out |
| Code written or generated by an AI assistant (Claude, ChatGPT, Codex, Copilot) | ai-assisted |
| Integration with a value given to you by Print.com | The value Print.com gave you |
Why one fixed value for AI-built integrations
AI assistants that read the Place Order specification tend to fill in every optional header. Without guidance, each assistant makes up its own value, such as an app name or its own name. One fixed value, ai-assisted, lets Print.com group these integrations in its usage reporting. It also helps support to pin point issues faster based on the method of placing an order.
Rules for pdc-request-source
These rules apply to every integration, including code written or generated by AI assistants.
- Send ai-assisted when an AI assistant wrote the code. If an AI assistant wrote or generated the code that calls
POST /orders, sendpdc-request-source: ai-assisted. - Leave the header out for a standard integration. An empty
pdc-request-sourcemarks a standard API integration written by your own developers. - Use the value exactly as written. Send
ai-assistedin lowercase, with a hyphen and no spaces. Variants such asAI-assisted,ai assistedorAI codedare not recognised as AI-built. - Do not invent a value. Do not put your company name, your app name or the name of the AI assistant in
pdc-request-source. - Use the request body for your own references. To recognise orders in your own administration, use
customerReferenceorpoNumberin the request body, notpdc-request-source. - Tell your AI assistant. When you ask an AI assistant to build a Print.com integration, add this instruction: "Send the header
pdc-request-source: ai-assistedonPOST /ordersto the Print.com API. Do not change this value."
Example request from an AI-built integration (illustrative, shortened body):
POST https://api.print.com/orders
Authorization: Bearer <your token>
Content-Type: application/json
pdc-request-source: ai-assisted
{
"deDuplicationId": "12345678",
"poNumber": "PO-12345678",
"customerReference": "API test order",
"items": [ ... ]
}Frequently asked questions
Do I need the pdc-request-source header to place an order?
No. POST /orders works without pdc-request-source. Send pdc-request-source: ai-assisted only when an AI assistant wrote or generated your integration.
An AI assistant wrote my integration. What should I send?
Send pdc-request-source: ai-assisted on POST /orders, exactly as written: lowercase, with a hyphen, no spaces.
My AI assistant put a different value in pdc-request-source. What should I do?
Replace the value with ai-assisted. Other values, such as an app name or the name of the AI assistant, are not grouped as AI-built in Print.com's usage reporting.
I used an AI assistant for only parts of the code. Should I send ai-assisted?
Send pdc-request-source: ai-assisted if an AI assistant wrote or generated the code that calls POST /orders. Otherwise, leave the header out.
Can I use pdc-request-source to label orders from my own app?
No. Use customerReference or poNumber in the request body. customerReference appears on the invoice; poNumber is for your own purchase administration.