Create a set of credential layout attributes

post

/fscmRestApi/resources/11.13.18.05/publicSectorCredentialLayouts

Request

Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Default Value: 1
    The unique identifier for a public sector agency.
  • Title: Attribute Code
    Maximum Length: 30
    A unique value that identifies the credential attribute.
  • Maximum Length: 120
    The label for a credential layout attribute.
  • Title: Enabled
    Maximum Length: 1
    Default Value: N
    Indicates whether the credential attribute is enabled or not.
  • Title: Required
    Maximum Length: 1
    Default Value: N
    Indicates whether the credential attribute is required or not.
  • Default Value: 0
    Indicates whether the row is seed data.The valid values are 0, 1, and 2 and they represent 0= customer data, 1= seed data cannot be modified, and 2= seed data can be modified.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : publicSectorCredentialLayouts-item-response
Type: object
Show Source
  • Default Value: 1
    The unique identifier for a public sector agency.
  • Title: Attribute Code
    Maximum Length: 30
    A unique value that identifies the credential attribute.
  • Maximum Length: 120
    The label for a credential layout attribute.
  • Title: Length
    Read Only: true
    The length of a credential layout attribute.
  • Title: Type
    Read Only: true
    Maximum Length: 128
    The type of a credential layout attribute.
  • Read Only: true
    Maximum Length: 1
    Default Value: N
    Indicates whether the record is logically deleted (Y or N). The valid values are Y = deleted record, and N=active record. The default value is N.
  • Read Only: true
    The display of a credential layout attribute.
  • Title: Enabled
    Maximum Length: 1
    Default Value: N
    Indicates whether the credential attribute is enabled or not.
  • Links
  • Title: Required
    Maximum Length: 1
    Default Value: N
    Indicates whether the credential attribute is required or not.
  • Default Value: 0
    Indicates whether the row is seed data.The valid values are 0, 1, and 2 and they represent 0= customer data, 1= seed data cannot be modified, and 2= seed data can be modified.
Back to Top