AportoTech

Getting Started with Aporto API

Welcome to Aporto. This guide walks you through the essential information you need to start integrating Aporto APIs into your product, including models, pricing, authentication, request flow, limits, and support. We aim to be transparent, practical, and developer-friendly. Please read this carefully before going to production.

1. Available Models & Playground

  • We continuously update and onboard new models as soon as they are stable.
  • Each model page links to its details, where you can test and experiment directly in our UI before calling the API.
  • The Playground (Chat) is the best place to understand model behavior, parameters, and output formats.
  • See all models on our Models page.

2. Pricing

  • Our prices are typically 30%–50% lower than official APIs.
  • For some models, discounts can reach up to 80%.
  • Pricing may change as upstream providers adjust their costs, so always refer to the Models page for the latest numbers.

3. Creating and Securing Your API Key

⚠️ Treat your API key as a secret.

  • Never expose your API key in frontend code (browser, mobile apps, public repositories).
  • Rate limits per key (hourly, daily, and total usage caps) are enforced.
  • Use environment variables on your backend to store keys securely.

4. API Base URL

https://api.aporto.tech/v1

This is an OpenAI-compatible endpoint. You can use it with the official OpenAI SDKs by changing the base_url.

5. Required Request Headers

Authorization: Bearer <YOUR_API_KEY>
Content-Type: application/json

If your key is invalid or missing, you will receive:

{"code":401,"msg":"You do not have access permissions"}

6. Logs & Task Details

  • We provide detailed logs for every request.
  • Creation time, Model used, Input parameters.
  • Task status, Credit consumption.
  • Final results or error details.

7. Data Retention Policy

  • Generated media files: stored for 14 days, then automatically deleted.
  • Log records (text / metadata): stored for 2 months, then automatically deleted.

8. Asynchronous Task Model

  • Requests return HTTP 200 and a task_id immediately.
  • You can provide a callback (webhook) URL in the request.
  • Or actively poll the “query record info” API using the task_id.

9. Rate Limits & Concurrency

  • Up to 20 new generation requests per 10 seconds.
  • This typically allows 100+ concurrent running tasks.
  • Limits are applied per account.
  • Excessive requests will be rejected with HTTP 429.

10. Developer Support

  • Get help regarding API integration or account issues.
  • Email us at: support@aporto.tech
  • Your data and conversations remain confidential.
  • We aim for fast and technical responses.

11. Stability Expectations

  • We are not perfect, but we strive for high availability.
  • Our overall stability may be slightly lower than official providers due to aggregation complexity.
  • This is a conscious trade-off for significantly lower prices and unified access.

12. About the Team

  • We move fast and care deeply about developer experience.
  • We are constantly improving our infrastructure.
  • Not everything is perfect, but we are transparent about it.
  • We can’t satisfy every use case immediately, but we listen to feedback.