Can AI Video Indexer add "callbackUrl" parameter for the Create Video Summary API?

Hi Justin,

Welcome to Microsoft Q&A,

You are right. The callbackUrl parameter is currently available in the Upload Video API but is not supported in the Create Video Summary API. This is a known gap and a valid ask.

For now, the current workaround is to poll using the Get Video Summary endpoint. Keep polling until the state moves out of Processing.

To Avoid Polling in Your App Code

If you want to keep your application clean, wrap the polling inside an Azure Durable Function using the async HTTP polling pattern, or use an Azure Logic Apps recurrence trigger. This offloads the wait loop entirely from your core application.

Feature Request

This has already been raised on the Azure Feedback portal. Go ahead and upvote it to push priority with the product team:

Feature Request: Add callbackUrl to Create Video Summary API

The Upload Video API already supports callbackUrl, so extending the same pattern to Create Video Summary is a reasonable and well-scoped ask.

If the answer is helpful, please click Accept Answer and kindly upvote it. If you have any further questions, feel free to comment.

Hey Justin,

Thank you for reaching out on the Microsoft Q&A.

At the moment, the Create Video Summary API does not support a callbackUrl parameter. Based on the current API surface, there’s no documented way to receive an asynchronous callback for summary completion, so the only supported approach today is to poll the summary status endpoint until the job is completed.

What you can do today

You can poll the summary status periodically, for example:

• Call the summary status endpoint
• Check for states like InProgress → Completed
• Introduce retry logic with delay (backoff) to avoid excessive calls

This polling pattern is commonly used with Video Indexer APIs when no callback is available.

In general, Video Indexer workflows rely on either polling or callbacks (where supported) for async operations [github.com]

Workarounds you can consider

1. Use Upload API callback + trigger summary flow

• The Upload Video API already supports callbackUrl
• You can use this to trigger a Function / Logic App once indexing completes
• From there:
  • Call Create Video Summary
    • Then handle polling in the background

This helps you avoid manual orchestration at the client level.

2. Implement a lightweight background polling mechanism

You can:

• Use a background worker (Azure Function / WebJob / Logic App loop)
• Add retry with exponential backoff
• Store intermediate state if needed

This is the most common workaround until callback support is added.

References:

• Create Video Summary API
• Video Indexer API overview
• Video Indexer API usage guide

I Hope this helps. Do let me know if you have any further queries.

Thankyou!