API Reference

TestAuto.app exposes three API versions, each designed for a different learning objective. Select an API below to view its complete endpoint reference.

API V1 — No Authentication

All CRUD endpoints for tasks. No login required. Perfect for learning the basics of REST API testing.

https://api.testauto.app/api/v1View reference →

API V2 — JWT Authentication

Same endpoints as V1 but requires a Bearer token. Includes login and token refresh endpoints.

https://api.testauto.app/api/v2View reference →

Buggy API

Intentionally unreliable API with random errors, delays, and inconsistent data. Practice resilient test patterns.

https://api.testauto.app/api/buggyView reference →

Common Concepts

Task Resource Schema

All three APIs work with the same Task structure:

id (integer) — Auto-assigned
title (string, required) — direct API create/update validation accepts 1–100 characters
description (string, optional) — direct API create/update validation accepts up to 500 characters
status (enum) — TODO | IN_PROGRESS | DONE
priority (enum) — LOW | MEDIUM | HIGH | URGENT
dueDate (date, optional) — YYYY-MM-DD
labels (string array, optional) — up to 10 free-text labels
checklistItems (array, optional) — ordered checklist items with text and done
comments (array) — ordered comment timeline attached to the task
attachments (array) — ordered attachment metadata with id, fileName, contentType, fileSizeBytes, and uploadedAt
sortOrder (integer) — manual board-order position within the current status column
createdAt (ISO 8601 timestamp, system-managed)
updatedAt (ISO 8601 timestamp, system-managed and refreshed on successful updates)

Attachment binary uploads use nested multipart endpoints rather than the JSON task create/update payloads. All three API versions cap tasks at 3 attachments and enforce a 1 MB per-file limit.

POST /tasks/{id}/attachments — upload one or more files via multipart/form-data using the files part name
DELETE /tasks/{taskId}/attachments/{attachmentId} — remove a stored attachment

Interactive Documentation

For interactive API exploration, use the Swagger UI.