Update user
PUT {{url}}/users/123-234-345-456
Update users
These calls are meant to mock how calls to update a user would behave.
Please review the example matching features that are being leveraged.
Commonly used example matching techniques are done by:
- Filter by HTTP method
- Filter by headers
x-mock-response-code
- The API call's response code, e.g.
200 OK
,201 Created
, etc.
- The API call's response code, e.g.
x-mock-response-id
- The UID of the example
x-mock-response-name
- The name of the example
- Filter by URL
- Filter by parameter keys and values
Custom Header and Request body matching
Another optional way to filter examples responses is using customer Header and Request body matching. These settings can be optionally configured under your [Mock Server's configuration page]
Wildcard variable setup
Create wildcard variable in example
Pass in value to wildcard variable in request (which is then reflected in the example response)
Request Body
{"firstName"=>"{{$randomFirstName}}", "lastName"=>"{{$randomLastName}}"}
HEADERS
Key | Datatype | Required | Description |
---|---|---|---|
x-mock-response-name | string | ||
x-mock-response-name | string | ||
x-mock-response-name | string | ||
x-mock-response-code | string | ||
x-mock-response-code | string | ||
x-mock-response-code | string | ||
x-mock-response-id | string | Update user (success). Note that this id will be different if you have forked the original collection | |
x-mock-response-id | string | Update user (unauthorized). Note that this id will be different if you have forked the original collection | |
x-mock-response-id | string | Update user (forbidden). Note that this id will be different if you have forked the original collection |