Skip to content

Auto generated schema based UPDATE MANY API

Table structure

customer_id first_name last_name last_update pincode isActive
1 Bob lin 2022-11-14 04: 34: 58 382345 1
2 Alice Page 2022-10-15 02: 10: 40 382346 1
3 Mallory Brown 2022-09-13 03: 44: 05 382347 1
4 Eve Mathly 2022-11-12 01: 59: 33 382348 1
5 Eve Page 2022-11-12 01: 59: 33 382349 1

Request Method: PUT

find and update the same key`s value.

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "first_name": "Alice"
    },
    "updateData": {
        "first_name": "MALLORY"
    }
}

find - $in, update many

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "customer_id": {
            "$in": [2, 3]
        }
    },
    "updateData": {
        "last_name": "Brown"
    }
}

find - $and, update many

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "$and": [
            {
                "first_name": "Alice"
            },
            {
                "pincode": 382345
            }
        ]
    },
    "updateData": {
        "last_name": "Page"
    }
}

find - $or, update many

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "$or": [
            {
                "first_name": "Alice"
            },
            {
                "pincode": 382345
            }
        ]
    },
    "updateData": {
        "last_name": "Page"
    }
}

find - $nin, update many

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "first_name": {
            "$nin": ["Alice", "Mallory"]
        }
    },
    "updateData": {
        "last_name": "Brown"
    }
}

find - $eq, update many

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "first_name": {
            "$eq": "MALLORY"
        }
    },
    "updateData": {
        "isActive": 1
    }
}

find - $gt, update many

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "customer_id": {
            "$gt": 3
        }
    },
    "updateData": {
        "isActive": 0
    }
}

find - $gte, update many

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "customer_id": {
            "$gte": 3
        }
    },
    "updateData": {
        "isActive": 1
    }
}

find - $lt, update many

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "customer_id": {
            "$lt": 2
        }
    },
    "updateData": {
        "isActive": 0
    }
}

find - $lte, update many

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "customer_id": {
            "$lte": 2
        }
    },
    "updateData": {
        "isActive": 0
    }
}

Nested find, update many [MongoDB]

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "customer_id": 2
    },
    "updateData": {
        "phone": 9662826853
    }
}

update in array using $(update) [MongoDB]

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "customer_id": 2,
        "ages.birth_year": 1889
    },
    "updateData": {
        "ages.$.age": 35
    }
}

sent as string $(update) [MongoDB]

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "customer_id": 2,
        "ages.birth_year": "1889"
    },
    "updateData": {
        "ages.$.age": "35"
    }
}

multiple $ parameter used $elemMatch, $gte, $lte [MongoDB]

URL 

/api/schema/user-path/instance/database/table/update-many
Request Payload 
{
    "find": {
        "customer_id": 2,
        "ages": {
            "$elemMatch": {
                "age": {
                    "$gte": 30
                },
                "birth_year": {
                    "$lte": 1900
                }
            }
        }
    },
    "updateData": {
        "ages.$.birth_year": 1991
    }
}

Supported headers

Header Description
x-am-response-case It will change the response keys text as requested case. 
"x-am-response-case": "camelCase"
noChange | camelCase | capitalCase | constantCase | dotCase | headerCase | noCase | paramCase | pascalCase | pathCase | sentenceCase | snakeCase
x-am-response-object-type To get flat response we use this request header. 
"x-am-response-object-type": "make_flat"
no_action | make_flat
x-am-meta To get the meta-data of requested API. 
"x-am-meta": "true"
false | true
x-am-secret Place secret id from API Maker. 
"x-am-secret": "6381b80359bdbd3a87c9abd5"
x-am-internationalization We can get backend error messages in any user language and directly show them to the user in UI, so the user can take appropriate actions.
Provide saved internationalization name in request header. 
"x-am-internationalization": "HINDI"
x-am-run-in-sandbox System will try to run requests in maximum provided sandbox, so if 1 provided every request will run in one sandbox, even if we have multiple sandbox with multiple API Maker instances. 
"x-am-run-in-sandbox": "0"
x-am-content-type-response We can provide response type in request header. As provided header value we can expect the response type. 
"x-am-content-type-response": "application/json"
application/json | text/xml | text/yaml
x-am-cache-control To reset the cache of the requested API manually and get fresh data, we can use 'x-am-cache-control' request header. 
"x-am-cache-control": "reset_cache"
no_action | reset_cache
x-am-get-encrypted-data Encrypt response data and get in to the response. 
"x-am-get-encrypted-data": "get_data_and_encryption"
no_encryption | get_only_encryption | get_data_and_encryption
x-am-authorization Provide token of API user in "x-am-authorization" header which will be generated from API Users inside API Maker. 
"x-am-authorization": "eyJhbGciOiJIUzI1NiIsdlRrblJlcS"
x-am-user-authorization User token should be provided in 'x-am-user-authorization' header which will be generated based on some database user if required. 
"x-am-user-authorization": "eyJhbGciOiJIpc1BydlRrblJlcS"
x-aws-authorization Provide AWS Cognito token in request header 'x-aws-authorization', if required. 
"x-aws-authorization": "eyJhbGciOiJIUc1BdlRrlJlcS"
x-google-authorization Provide Google user token in request header 'x-google-authorization', if required. 
"x-google-authorization": "eyJhbGceyJpc1BdlRrlJlcS"
x-azure-authorization Provide Azure active directory token in request header 'x-azure-authorization', if required. 
"x-azure-authorization": "eyJhbGciOiJIUzI1NiIJpc1BdlRrlJlcS"
x-no-compression If user do not send 'x-no-compression' in request header, and response characters are more than value of "maxCharsResToCache" than the response will be compressed. 
"x-no-compression": "true"
x-am-sandbox-timeout If any API did not give a response within given time, the sandbox will break and give a proper error message in the response. 
"x-am-sandbox-timeout": "13000"  // milliseconds
x-am-encrypted-payload When user sent encrypted payload, user must have to sent "x-am-encrypted-payload:true". 
"x-am-encrypted-payload": "true"