Update, commit, or deploy prompts in bulk
Process 1 to 100 prompt operations sequentially in request order using exact prompt_id matching. Each item runs in its own transaction, so a failed item is rolled back without undoing successful items. update changes model configuration on the latest draft and does not accept content fields such as messages, variables, or description; commit snapshots the latest draft; deploy promotes the latest committed version. A later duplicate successful commit or deploy for the same prompt in one request is returned as an indexed error. This endpoint inherits the caller’s configured API-key or JWT rate limits; it has no fixed endpoint-specific RPM.
Authentication
Use your Respan API key for Respan API authentication. Enter only the Respan API key value; clients send Authorization: Bearer <RESPAN_API_KEY>. For /api/responses, provider credentials such as Perplexity, OpenAI, or Azure OpenAI go in Settings -> Providers or respan_params.credential_override in the request body, not in this authentication field.
Use a dashboard JWT only for dashboard-authenticated endpoints. Respan API-key endpoints use the respanApiKey auth field instead.
Request
Prompt operations. Error indices refer to this zero-based array.
Response
Item-level failures, keyed by zero-based input index.