Skip to main content

Nextry API

Nextry API provides asynchronous image-generation workflows for fashion, product, and interior use cases.

Base URL​

<base_url>

If your team uses a private deployment, use the base URL provided during onboarding.

Source of Truth​

For request/response field-level contracts, treat your OpenAPI spec as the source of truth:

  • Local Swagger UI: http://localhost:8000/docs
  • Exported OpenAPI JSON (if enabled): GET /openapi.json

This Docusaurus site focuses on integration patterns, endpoint intent, and operational behavior.

API Behavior​

  • Authentication: Authorization: Bearer <api_key>
  • Request style: mostly application/json and multipart/form-data
  • Tool discovery endpoint: GET /generation/tools
  • Generation type discovery endpoint: GET /generation/generationTypes?tool=<tool>
  • Generation model: asynchronous jobs with status polling
  • Common history statuses: pending, complete, error

Typical Integration Flow​

  1. Request API token from Nextry support.
  2. Configure Authorization: Bearer <api_key> in your backend.
  3. Fetch available tools via GET /generation/tools.
  4. Fetch generation types via GET /generation/generationTypes?tool=<tool>.
  5. Submit generation request to POST /generation/generate_image_v2/.
  6. Receive history_item_id and image URLs from response.
  7. Poll history/details endpoint until status is terminal.

Example:

Environments​

Use separate credentials per environment:

  • Development
  • Staging
  • Production

This reduces blast radius during key rotation and incident response.

Support​