title: Is it not possible to use curl, to use Google Cloud Speech API, to recognize within 10 to 15 minute files?
body: <p>I'm using REST API with cURL because I need to do something quick and simple, and I'm on a box that I can't start dumping garbage on; i.e. some thick developer SDK.</p>
  
  <p>I started out <code>base64</code> encoding <code>flac</code> files and initiating <code>speech.syncrecognize</code>.</p>
  
  <p>That eventually failed with:</p>
  
  <pre><code>{
    "error": {
      "code": 400,
      "message": "Request payload size exceeds the limit: 10485760.",
      "status": "INVALID_ARGUMENT"
    }
  }
  </code></pre>
  
  <p>So okay, you can't send 31,284,578 bytes in the request; have to use Cloud Storage. So, I upload the flac audio file and try again using the file now in Cloud Storage. That fails with:</p>
  
  <pre><code>{
    "error": {
      "code": 400,
      "message": "For audio inputs longer than 1 min, use the 'AsyncRecognize' method.",
      "status": "INVALID_ARGUMENT"
    }
  }
  </code></pre>
  
  <p>Great, <code>speech.syncrecognize</code> doesn't like the content size; try again with <code>speech.asyncrecognize</code>. That fails with:</p>
  
  <pre><code>{
    "error": {
      "code": 400,
      "message": "For audio inputs longer than 1 min, please use LINEAR16 encoding.",
      "status": "INVALID_ARGUMENT"
    }
  }
  </code></pre>
  
  <p>Okay, so <code>speech.asyncrecognize</code> can only do LPCM; upload the file in <code>pcm_s16le</code> format and try again. So finally, I get an operation handel:</p>
  
  <pre><code>{
    "name": "9174269756763138681"
  }
  </code></pre>
  
  <p>Keep checking it, and eventually it's complete:</p>
  
  <pre><code>{
    "name": "9174269756763138681",
    "done": true,
    "response": {
      "@type": "type.googleapis.com/google.cloud.speech.v1beta1.AsyncRecognizeResponse"
    }
  }
  </code></pre>
  
  <p>So wait, after all that, with the result now sitting on a queue, there is no <code>REST</code> method to request the result? Someone please tell me that I've missed the glaringly obvious staring me right in the face, and that Google didn't create completely pointless, incomplete, REST API.</p>