Strange json response /api/v1/product

Hi,

I’m working on a small connector between a shopware 6 test environment and another database which is gathering product data from sw.
Now, I moved the project over to a new computer and from that point on the json result looks totally different and as you can see a lot of data is missing. 

Im calling my shopware client to get all products (  $response = $service->request( ‘GET’, ‘product’);  )
But all what I get it this:
 

array (size=5)
  'data' => 
    array (size=1)
      0 => 
        array (size=6)
          'id' => string '960e95dbb6f6439a9d4339722c7d773e' (length=32)
          'type' => string 'product' (length=7)
          'attributes' => 
            array (size=56)
              ...
          'links' => 
            array (size=1)
              ...
          'relationships' => 
            array (size=20)
              ...
          'meta' => null
  'included' => 
    array (size=2)
      0 => 
        array (size=6)
          'id' => string '6c54c4683bf042b7848e51738745d25d' (length=32)
          'type' => string 'tax' (length=3)
          'attributes' => 
            array (size=5)
              ...
          'links' => 
            array (size=1)
              ...
          'relationships' => 
            array (size=1)
              ...
          'meta' => null

The result is totally different from what I expected or what is documented. I mean, yes, it is an result and f.e. the ID that I get back it ok. I also can filter for specific product and get at least the correct ID back without any error.
If I run the same code on the old machine I get a lot more product information (sadly I cannot paste the result here yet) 

I already recreated the integration. Access-ID and Seq.Key looks ok to me. I also get an authorisation error when I use random Id and key. I thought its permission related, thats why.

Can somebody explain this result set? is something missing? 

Would be great to get an idea, thx

 

I updated my webserver. Now I have the complete json visible including “attributes” and so on. 
Issue can be closed.