title: Diff between web routing and api routing in laravel 5.3
body: <p>I read many post regarding new concept about api routing. I understood that api routing is used for mobile platforms but is there code level difference between them</p>
  
  <p>In <code>RouteServiceProvider</code> i can see</p>
  
  <pre><code>/**
       * Define the "web" routes for the application.
       *
       * These routes all receive session state, CSRF protection, etc.
       *
       * @return void
       */
      protected function mapWebRoutes()
      {
          Route::group([
              'middleware' =&gt; 'web',
              'namespace' =&gt; $this-&gt;namespace,
          ], function ($router) {
              require base_path('routes/web.php');
          });
      }
  
      /**
       * Define the "api" routes for the application.
       *
       * These routes are typically stateless.
       *
       * @return void
       */
      protected function mapApiRoutes()
      {
          Route::group([
              'middleware' =&gt; 'api',
              'namespace' =&gt; $this-&gt;namespace,
              'prefix' =&gt; 'api',
          ], function ($router) {
              require base_path('routes/api.php');
          });
      }
  </code></pre>
  
  <p>As per this web route uses </p>
  
  <blockquote>
    <p>These routes all receive session state, CSRF protection, etc.</p>
  </blockquote>
  
  <p>api route </p>
  
  <blockquote>
    <p>These routes are typically stateless.</p>
  </blockquote>
  
  <p>My question is</p>
  
  <ol>
  <li><p>What does it mean <code>stateless</code> in api route ?</p></li>
  <li><p>Web routing uses  <code>session state</code>, <code>CSRF protection</code>. Does it mean api routing is not using session state, CSRF protection ?</p></li>
  <li><p>Laravel 5.3 uses seperate <code>web</code> and <code>api</code> routing, is there any advantages  ?</p></li>
  </ol>