Contex URL format and Create Account Operation

[mario_rod (Mario Rodrigues)]

Hello,

A couple of questions:

1) How can an account attribute be passed in an operation’s Context URL like “Get Object”?

Eg: Based on the account schema below, how could the uuid and userId be passed in?
/v3/employees/[**uuid**]/users/[**userId**]
Would it be something like /v3/employees/$plan.nativeIdentity.uuid$/users/$plan.nativeIdentity.userId$

{
    "status": {
        "code": 200,
        "message": "Request completed fine, no errors"
    },
    "users": [
        {
            "uuid": "jhdfgi04090cb1e1c288d00775e9fe",
            "userId": 234523,
            "firstName": "Johnny",
            "firstNameSort": "Johnny",
            "lastName": "Black",
            "lastNameSort": "Black",
            "organization": "Enron",
            "organizationSort": "Enron",
            "roleType": "ADMIN",
            "keyContact": true,
            "isPlaceholderUser": false,
            "officePhone": "123456789",
            "status": "ACTIVE",
            "createdBy": {
                "firstName": "Alvin",
                "lastName": "Smith",
                "firstNameSort": "Alvin",
                "lastNameSort": "Smith"
            },
            "createdOn": {
                "milliseconds": 1730760279000
            },

2) “Create Account”,

• does a response mapping need to be configured if we’re only interested in the status?
• In the Body/POST, what should the attribute values be? Is it the technical names from the identity profile or the attributes from the account schema? The docs show
  $plan.firstName$, $plan.officePhone$, etc but its not clear where those are from

[Santhakumar (Shantha Kumar)]

@mario_rod I am not sure first option but for Create Account you can always use $plan.firstName and $plan.userID based on the attribute name that we have used in create account page.

I have used the above condition in the create operation body it works fine for me. LMK if it helps.

Thanks.