​

API overview

Moveat APIs are not currently intended as a third-party integration product. They exist to support the web app and Agent. This page explains API areas at a high level.

​

API categories

​

Public APIs

Public APIs support web flows:

• Auth signup/login/logout.
• Google login.
• Current session/user info.
• Onboarding.
• Profile and context reads.
• Channel linking.
• Meal tracking.
• Weight tracking.
• Workout tracking.

These APIs authenticate with the user’s web session.

​

Internal APIs

Internal APIs support Agent flows:

• Resolve a user by linked channel.
• Fetch user context.
• Log meal entries idempotently.
• Fetch today’s nutrition summary.
• Log workouts and weight entries.

These APIs authenticate with an internal service token. They should be clearly marked as Agent-only in Swagger.

​

Error model

API errors should be structured and include a correlation ID when possible. This allows operations to search logs in Grafana/Loki. Common error types:

​

Swagger usage

Swagger is useful for inspecting the live API contract. The business documentation should explain flows and decisions; Swagger should explain exact request and response shapes.