Manage AIQ Repository Configuration with REST APIs

Last reviewed: September 22, 2026

Use these repository REST APIs only for supported AIQ administration and automation workflows. Treat repository names, branch data, and credentials as sensitive operational configuration.

Recommended guidance

• Use least-privilege accounts or tokens for repository automation.
• Validate API behavior in a non-production environment before automating changes.
• Avoid storing repository credentials or tokens in documentation, scripts, or logs.

Validation workflow

1. Confirm the AIQ version and supported repository API endpoints.
2. Authenticate with an approved account and call read-only endpoints first.
3. Validate repository name, branch, and status responses before triggering pull or save operations.
4. Log execution IDs and non-sensitive response details for traceability.
5. Review and rotate credentials used by repository integrations.

Note: Delete and save operations can change repository configuration. Use them only with explicit admin intent.

Last updated: September 22, 2026

If you have feedback on this topic, contact documentation@appvance.ai.