.jpg)
Two Fifteen API
Connect your platform to Two Fifteen
Build print-on-demand fulfilment into the website, app or order system your business already uses. Send orders to Two Fifteen, then bring progress and tracking data back into your own customer experience.
Build around the way your business works
The API gives your team a direct route between your system and the Two Fifteen order workflow.
Create an integration for a custom storefront, a sales platform or an internal order tool. Your business controls the experience; Two Fifteen receives the structured order details needed to move each job forward.
.jpg)
Connect your own platform
Link a customer-facing website, an app or a back-office system to the Two Fifteen order workflow.
.jpg)
Pass each order clearly
Send the customer, delivery, item, option, quantity and artwork details that belong to the order.
.jpg)
Bring progress back
Retrieve order, fulfilment, shipping and tracking data for your own operations and customer communications.
What you can build with the API
Create orders from your system
Submit a new order from the platform or workflow your business already runs.
Read one order in detail
Retrieve the complete available record for a specific Two Fifteen order.
Work with order lists
Bring groups of orders into an internal view, reconciliation process or operational tool.
Filter to the orders you need
Narrow order lists by identifiers, creation dates or current status instead of handling every record at once.
Count matching orders
Return the number of orders that meet your chosen filters for a concise operational check.
Follow order status
Read the current documented order state as the job moves through the Two Fifteen workflow.
Use fulfilment and tracking data
Retrieve fulfilment details, carrier information, tracking numbers and tracking links when they are available.
Carry the right order context
Keep external references, customer and delivery details, brand, item options, quantities, mock-ups, print files and label choices tied to the order.
Shape the hand-off around your order
Your integration can preserve the context your team needs instead of reducing every job to a basic product and address.
Use your own order reference alongside the buyer and delivery details. Pass the selected brand, line items, quantities and options, then include mock-up and print-ready artwork links for each decorated area where the order requires them.
That structure makes the API useful for more than a single storefront. The same order route can sit behind a marketplace, a client portal or an internal system, provided your development team maps the data to the documented Two Fifteen fields.
.jpg)
From your system to customer delivery
.jpg)
Get your access details
Open API Settings in your Two Fifteen account to find the credentials your integration uses to identify and sign each request.
.jpg)
Map the order
Connect your own order reference, customer and delivery details, items, quantities, options and artwork data to the documented order structure.
.jpg)
Submit and monitor
Create the order from your system, then retrieve order records and status data as your workflow needs them.
.jpg)
Bring delivery information back
Use returned fulfilment, carrier and tracking details inside your own operations or customer communications as the finished order moves towards delivery.
Keep customers inside the experience you built
Your storefront, platform or portal remains the place your customers recognise. The API handles the order connection behind it.
Two Fifteen order records can return status, fulfilment and shipping details, including carrier and tracking information when available. Your integration can use that data in the tools your team already works with and in the customer updates that suit your service.
The API does not prescribe one front end or one operating model. It gives your developers a documented order route that can be shaped around the business you already run.
.jpg)
Two Fifteen API questions
Is the Two Fifteen API right for my business?
It is designed for businesses that need a custom order connection rather than relying only on a ready-made store integration. You will need development resource to build and maintain the connection.
Can I use the API to create products or publish listings?
The current documentation covers order creation, retrieval, filtering, counts and deletion. It does not document product-catalogue, product-creation or listing-publication endpoints.
What information can I include with an order?
The documented order structure includes external references, customer and delivery details, brand, items, quantities, options, mock-up links, print-file links and label information where relevant.
Can my system check order progress and tracking?
Yes. Retrieved order records can include status, fulfilment, carrier, tracking number and tracking URL data when those details are present.
Does the API work with JSON or XML?
Yes. The documentation supports both JSON and XML requests and responses.
How are API requests authenticated?
Your Two Fifteen API Settings provide an AppID and Secret Key. Your integration uses them to identify the request and generate the required signature; the documentation explains the exact method.