73 MCP tools + full REST API

TutuPrints API docs

Use the REST API or MCP protocol to let an AI assistant handle photo printing, document printing, order management and every other operation directly.
Supports 21 mainstream AI clients including Claude, Gemini, Codex and Copilot.

Quick start

Integrate in three steps and start using AI for printing right away.

Register an account

Visit the TutuPrints website and register quickly with a phone verification code.

Create an API Key

On the “API keys” page in your account center, create a key with one click and use it right away.

Make a request

Call the REST API with your API Key, or configure it in an AI client to use MCP.

Authentication

All API requests authenticate by carrying the API Key in an HTTP header.

Authorization: Bearer tk_YOUR_API_KEY

Base URL

https://tutupp.com

Response format

Content-Type: application/json

MCP endpoint

POST https://tutupp.com/api/mcp

Open platform: after registering, create an API Key with no approval needed and use all API and MCP features immediately.

MCP integration

MCP (Model Context Protocol) is an open protocol from Anthropic that lets AI assistants call external tools directly.

Once configured, you can use natural language to have the AI run the full “upload document → create order → pay with balance” flow.

Protocol info

Endpoint: https://tutupp.com/api/mcp

Protocol: JSON-RPC 2.0 over Streamable HTTP

Methods: initialize · tools/list · tools/call

File upload: Supports the multipart/form-data extension (message part + file parts, zero base64, 100MB+) and standard application/json

Choose your AI client 21

Claude Code — mcs_desc_cli

Add (Add)

claude mcp add --transport http tutuprints https://tutupp.com/api/mcp --header "Authorization: Bearer tk_YOUR_API_KEY"

Add --scope user for global, --scope project for the current project only

Replace key (Replace)

claude mcp remove tutuprints && claude mcp add --transport http tutuprints ...(new key)

Remove (Remove)

claude mcp remove tutuprints

AI conversation example

You: Print report.pdf from my desktop, A4 black & white, and pay with my balance

AI calls automatically:

1. upload_document → Upload the file

2. get_print_prices → Look up A4 B&W pricing

3. create_order → Create the order

4. pay_with_balance → Pay with balance

AI: Done! Order PP2026040612345, A4 B&W ×1, ¥0.50 deducted from your balance.

REST API reference

An API Key can access all the endpoints below, covering every feature in the UI.

adt0

POST /api/documents/upload add0

GET /api/documents add1

GET /api/documents/{id} add2

DELETE /api/documents/{id} add3

adt1

POST /api/photos/upload add4

GET /api/photos/{id} add5

DELETE /api/photos/{id} add6

GET /api/photos/{id}/quality-check?size={size} add7

adt2

POST /api/orders add8

GET /api/orders add9

GET /api/orders/{id} add10

PUT /api/orders/{id}/cancel add11

GET /api/orders/track/{order_no} add12

GET /api/orders/{id}/tracking add13

adt3

POST /api/payment/create add14

POST /api/payment/balance add15

GET /api/payment/status/{order_id} add16

adt4

GET /api/user/balance add17

POST /api/user/balance/topup add18

GET /api/user/balance/transactions add19

adt5

GET /api/user/coupons add20

GET /api/user/coupons/available add21

POST /api/user/coupons/redeem add22

adt6

GET /api/addresses add23

POST /api/addresses add24

PUT /api/addresses/{id} add25

DELETE /api/addresses/{id} add26

POST /api/addresses/parse add27

adt7

GET /api/user/pre-orders add28

POST /api/user/pre-orders add29

GET /api/user/pre-orders/{id} add30

PUT /api/user/pre-orders/{id} add31

PUT /api/user/pre-orders/{id}/status add32

POST /api/user/pre-orders/{id}/submissions/{sid}/review add33

PUT /api/user/pre-orders/{id}/submissions/{sid}/cancel add34

adt8

GET /api/share/{code} add35

POST /api/share/{code}/submit add36

GET /api/share/{code}/submissions/{sid} add37

GET /api/share/{code}/my-submissions add38

adt9

GET /api/user/after-sales add39

POST /api/after-sales add40

adt10

GET /api/regions add41

GET /api/regions/{id} add42

GET /api/regions/tree add43

GET /api/regions/coverage add44

GET /api/regions/{city_id}/city-coverage add45

GET /api/regions/{id}/express-delivery add46

GET /api/regions/{id}/pickup-points add47

GET /api/agents/referral/{code} add48

GET /api/shipping/config add49

GET /api/shipping/carriers add50

adt11

GET /api/prices add51

GET /api/print-options/sizes add52

GET /api/print-options/paper-types add53

adt12

POST /api/photos/{id}/restore add54

GET /api/restorations/{id} add55

adt13

GET /api/auth/me add56

PUT /api/auth/me add57

adt14

GET /api/printer/status add58

GET /api/print-queue/status add59

GET /api/orders/auto-print-schedule add60

adt15

GET /api/user/api-keys add61

POST /api/user/api-keys add62

DELETE /api/user/api-keys/{id} add63

adt16

GET /api/health add64

MCP tool list73

All the tools below can be called via the MCP protocol; AI clients discover them automatically once configured.

adt17

upload_document add65 file_url | content | file_path, filename?

list_documents add66

get_document_info add67 document_id

delete_document add68 document_id

adt18

upload_photo add69 file_url | content | file_path, filename?

get_photo add70 photo_id

delete_photo add71 photo_id

check_photo_quality add72 photo_id, size

adt19

create_order add73 items[], delivery_method?, shipping_carrier_id?, coupon_id?

list_orders add74

get_order_status add75 order_id

cancel_order add76 order_id

track_order add77 order_no

get_order_tracking add78 order_id

adt20

create_payment add79 order_id, payment_method?

pay_with_balance add80 order_id

get_payment_status add81 order_id

create_topup add82 amount, payment_method?

get_balance add83

get_balance_transactions add84 page?, page_size?

adt21

list_coupons add85 scope?

get_available_coupons add86 amount?, scope?

redeem_coupon add87 code

adt22

list_addresses add88

create_address add89 name, phone, country, province, city, district, detail, ...

update_address add90 address_id, ...

delete_address add91 address_id

parse_address add92 text, country

adt23

list_pre_orders add93

create_pre_order add94 title, order_type, spec_mode, ...

get_pre_order add95 pre_order_id

update_pre_order add96 pre_order_id, ...

update_pre_order_status add97 pre_order_id, status

review_submission add98 pre_order_id, submission_id, approved, reject_reason?

cancel_submission add99 pre_order_id, submission_id

adt24

get_share_info add100 share_code

submit_share_photos add101 share_code, photo_ids[], password?, ...

get_submission_status add102 share_code, submission_id

list_my_submissions add103 share_code

adt25

list_after_sales add104

create_after_sales add105 order_id, type, reason, ...

adt26

list_regions add106 level?, parent_id?, search?

get_region add107 region_id

get_region_tree add108

get_region_coverage add109

get_city_coverage add110 city_id

get_agent_by_referral add111 referral_code

check_express_delivery add112 region_id

get_shipping_config add113

get_shipping_carriers add114

list_pickup_points add115 region_id

adt27

get_print_prices add116

get_print_options add117

get_printer_status add118

get_queue_status add119

adt28

get_profile add120

update_profile add121 nickname

adt29

restoration_preview add122 photo_id

get_restoration add123 restoration_id

create_restore_share add_sh1 restoration_ids[], message?, expire_days?, max_claims?, with_passcode?

list_my_restore_shares add_sh2 page?, limit?

revoke_restore_share add_sh3 share_id

claim_restore_share add_sh4 code, passcode?

adt30

list_api_keys add124

create_api_key add125 name, expires_in_days?

revoke_api_key add126 api_key_id

adt31

health_check add127

get_auto_print_schedule add128

adt32

submit_order_review add129 order_id, rating_print, rating_shipping?, rating_service?, comment?

batch_submit_order_reviews add130 items[{order_id, rating_print, ...}]

list_my_order_reviews add131 page?, limit?

get_order_review add132 review_id

mark_order_review_read add133 review_id

Code examples

A full example of the “look up prices → upload file → create order → pay with balance” flow.

# Query prices
curl https://tutupp.com/api/prices \
  -H "Authorization: Bearer tk_YOUR_API_KEY"

# Upload document
curl -X POST https://tutupp.com/api/documents/upload \
  -H "Authorization: Bearer tk_YOUR_API_KEY" \
  -F "file=@report.pdf"

# Create order
curl -X POST https://tutupp.com/api/orders \
  -H "Authorization: Bearer tk_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "items": [{
      "document_id": "uuid-here",
      "size": "A4",
      "paper_type": "matte",
      "quantity": 1
    }],
    "delivery_method": "pickup"
  }'

# Pay with balance
curl -X POST https://tutupp.com/api/payment/balance \
  -H "Authorization: Bearer tk_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"order_id": "uuid-here"}'

Typical workflow

Upload file Look up prices Create order Pay with balance Done

Error handling

The API uses standard HTTP status codes; error responses contain error info in JSON.

// Error response format
{
  "error": "Error description"
}

400

add134 ade0

401

add135 ade1

403

add136 ade2

404

add137 ade3

409

add138 ade4

413

add139 ade5

422

add140 ade6

429

add141 ade7

500

add142 ade8

Rate limiting: only sensitive write operations like login / register / verification codes are protected against attacks; normal usage never triggers it, and thresholds are configurable in the admin console. Responses carry a retry_after_seconds field + a Retry-After header.

Ready to get started?

Manage API keys