Skip to main content
POST
  1. After submission, a task_id will be returned. If you provided a callback_url, when the task status becomes finished or failed, a POST request will be sent to the callback_url.
  2. Regardless of whether callback_url is provided, you can retrieve the result through the unified Query Task Status endpoint.
Tripo3D H3.1 supports high-detail text-to-3D, single image-to-3D, and multiview-to-3D generation through three public model IDs.

Models

  • tripo3d-h3.1-text-to-3d - Generate a high-detail 3D model from a prompt
  • tripo3d-h3.1-image-to-3d - Generate a 3D model from one object image
  • tripo3d-h3.1-multiview-to-3d - Generate a 3D model from 2-4 views of the same object

Required parameters

  • model: tripo3d-h3.1-text-to-3d, tripo3d-h3.1-image-to-3d, or tripo3d-h3.1-multiview-to-3d
  • input.prompt: Required for tripo3d-h3.1-text-to-3d
  • input.image_urls: Required for image models. Use exactly one item for image-to-3D; use 2-4 items for multiview-to-3D

Optional parameters

  • negative_prompt: Text-to-3D only. Features to avoid
  • face_limit: Target face count, from 1000 to 2000000
  • texture: Whether to generate textures. Default is true
  • pbr: Whether to generate PBR materials when textures are enabled
  • model_seed, image_seed, texture_seed: Optional integer seeds
  • texture_quality: standard or detailed. Default is standard
  • geometry_quality: standard or detailed. Default is standard
  • auto_size: Whether to auto-scale the model
  • quad: Whether to generate quad mesh topology
  • callback_url: Optional webhook URL for task completion notification

Output

The task result is returned as a file list. Available items may include:
  • model_glb
  • thumbnail
  • entries from model_urls, such as glb, base_model, and pbr_model, when available
Each file item includes label, file_url, file_type, format, content_type, file_name, and file_size when available.

Notes

  • Multiview inputs should show the same object from different angles.
  • The API returns asynchronous task status. Poll the unified task status endpoint or use callback_url.

Authorizations

Authorization
string
header
required

All API endpoints require Bearer Token authentication.

Create an API key: sign in to PoYo, open Dashboard → API Key at poyo.ai/dashboard/api-key, and click to create a key.

Add it to the request header:

Body

application/json
model
enum<string>
required
Available options:
tripo3d-h3.1-text-to-3d,
tripo3d-h3.1-image-to-3d,
tripo3d-h3.1-multiview-to-3d
input
object
required
callback_url
string<uri>

Response

Task submitted successfully

code
enum<integer>
required

Business status code. 200 means success; any other value means the request failed. Always check this field: some validation errors return HTTP 200 with code: 400 in the body.

  • 200: Success
  • 400: Invalid request parameters
  • 401: Missing or invalid API key
  • 402: Insufficient credits
  • 403: Permission denied
  • 404: Resource not found
  • 408: Request timeout
  • 429: Rate limit exceeded
  • 500: Internal server error
  • 502: Upstream service error
  • 503: Service unavailable

See Error Codes for details.

Available options:
200,
400,
401,
402,
403,
404,
408,
429,
500,
502,
503
Example:

200

data
object
required