What happens if a lookup takes too long to return a response? How do retryId and callbackUrl work?

If a lookup runs longer than ~20 seconds, the API returns a retryId instead of holding the HTTP connection open. You can poll with that retryId until the request completes (only the successful final result is billed). For smoother workflows, you can also send a callbackUrl with your request—Cobalt will immediately return a requestId, then POST the completed results to your callback endpoint once ready. Both patterns are supported; callback is recommended for batch or high-volume use