APIM REST API - How to add an API with operations?

Question

When I issue a PUT to /apis/{aid} with import=true and contentType = application/json, I get an 400 BadRequest if the body contains operations.  Note that I'm
not using WADL or Swagger format, and am building the JSON request body instead as per the documentation.  
The error returned in the response body is:
{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"operations","message":"Invalid
field 'operations' specified"}]}}
If I omit the operations field from the request body, the API is created correctly (but with no operations of course).  
To illustrate, here is the RAW request (slightly modified to remove the authorization and instance names):
PUT https://testinstance.management.azure-api.net/apis/123456?api-version=2014-02-14-preview&import=true HTTP/1.1
Authorization: SharedAccessSignature . . .
Content-Type: application/json; charset=utf-8
Host: testinstance.management.azure-api.net
Content-Length: 414
Expect: 100-continue
Connection: Keep-Alive
{"name":"Customer","description":"This API is used to manage customers","serviceUrl":"http://www.somewebsite.com/customers","path":"customers","protocols":["http","https"],"operations":[{"id":"/apis/123456/operations/a04b16da-29b7-44f5-95a3-25603dbc9b6d","name":"Customer
(Get)","description":"Returns information about the customer with the specified ID.","method":"GET","urlTemplate":"/customers/{customerId}"}]}
The JSON looks correct to me - can anyone spot what I'm doing wrong?  Can you provide a RAW request that works?
Note also that I've not included the "path" query string parameter, even though the documentation suggests that it is required when import=true.  Since there is no easy way to update APIs/Operations en masse, I'm having to resort to driving
the APIM REST API and could use some additional documentation for this specific operation.

Answer 1

Just updating this thread with the answer...my request body was malformed - I was using an array of objects for the operations field instead of a complex object representing the collection.
So instead of this:
"operations": [
...I should have been using this:
"operations": {
    "value": [
You can see the correctly formatted payload in the sample response body returned from the
GetApi endpoint.
Thanks to Vlad for pointing out my mistake!