Provisioning track · 3 min

Build a SCIM PATCH

Fill a form, get the exact JSON a SCIM client would send.

The idea

1PATCH changes only what you name
A SCIM PATCH carries a list of operations. Untouched fields stay as they are.
2Each operation has three parts
An op (add, replace or remove), a path to the attribute, and usually a value.
3The wrapper is fixed
Every request names the PatchOp schema URN in schemas. A server may reject it without that.
4Try it
Choose an operation below and watch the JSON build. Then send it to the simulated server.

Try it

Build the request

Pick the operation and value. The JSON updates as you type.

This exercise needs JavaScript. Here is the answer key.

example requestSimulated output

$ PATCH /scim/v2/Users/8f2a
{"schemas":["urn:ietf:params:scim:api:messages:2.0:PatchOp"],"Operations":[{"op":"replace","path":"active","value":false}]}

Check yourself

1 of 3 Which op sets active to false?

2 of 3 What does the schemas list hold in a PATCH?

3 of 3 Which standard defines the protocol?

Answer key

Which op sets active to false? replace. It overwrites an existing attribute value.
What does the schemas list hold in a PATCH? The PatchOp URN. urn:ietf:params:scim:api:messages:2.0:PatchOp.
Which standard defines the protocol? RFC 7644. RFC 7643 defines the schema and RFC 7644 the protocol.