Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

3.0.0

The FlexAttribute API is used to create, update or delete flex attribute definitions. A flex attribute is a custom data input field that is used to collect additional information that was not originally designed into the mobile application.

Resource URL Summary

/seiapi/v3/trans/FlexAttribute/${FlexAttrID}

API Specific Parameters

ParameterDescription

${FlexAttrID}

Identifies the unique flex attribute object.

Supported HTTP Methods

MethodDescription
GET

Returns the flex attribute definition identified by the ${FlexAttrID} URL parameter.

PUTCreates a new flex attribute definition identified by the ${FlexAttrID} URL parameter. If the flex attribute definition already exists and error will be returned.
POSTUpdates the existing flex attribute definition identified by the ${FlexAttrID} URL parameter.
DELETE

Deletes an existing flex attribute definition, identified by ${FlexAttrID} URL parameter. If the object does not exists or has been deleted, a soft warning is returned.

(info) A request body is not required for the DELETE method.

HTTP Headers

This API uses the default ServiceMobility HTTP Headers.

HTTP Body

The body contains a single FlexAttr object in the format specified on the URL. 

JSON Format
{
	"Default": "",
    "Desc": {
        "en": "English description",
        "es": "Spanish description"
    },
    "FlexAttrID": "",
    "InputType": 1001,
    "IsActive" : true,
    "IsReq": false,
    "Label": {
        "en": "English label",
        "es": "Spanish label"
    },
    "Max": 0.0,
    "Min": 0.0,
    "Precision": 0,
    "Rules": "",
    "Selections": [
        {
            "Code" : "",
            "Text": {
                "en": "English label",
                "es": "Spanish label"
            },
        }
    ]
}

HTTP Response

Response Codes

HTTP CodeDescription

200

OK. Request was processed successfully.

(info) Even though the request may return a successful code of 200, the body may still contain warning details.

400

Syntax error in request. The response body will provide more details on the specific reason. Verify the URI, its parameters, and request body.

401

Unauthorized. The credentials are incorrect, please verify and try again.

404

Not Found. The URL is incorrect, please verify and try again.

405

The specified HTTP method is not supported for this resource.

409

Conflict. This error usually occurs when attempting to overwrite an existing object that can not be replaced.

410

The specified object does not exists. Please verify the URI.

500

An error has occurred within ServiceMobility. Please review the error message details and if necessary, contact customer support.

Response Body

{
    "code": 400,
    "detail": {
        "message": "",
        "params": {
            "value": ""
        },
        "dataPath": ""
    }
}

Response Object Properties

PropertyTypeDescription
codeintegerThe HTTP response code.
detailobject

This object provides additional details the system provided while processing the transactions. Usually the details provide additional information on why an error occurred. However, it may also provide warning details even when the requests was successful. For example, the request may have returned a response of 200=OK, but included warnings in the response body of properties that are still being used that are marked for deprecation.

PropertyTypeDescription
messagestringA human readable message related to the processing of the request.
paramscollectionA collection of additional key/value pairs that contain the values that caused the warning/error condition.
dataPathstringIdentifies the location within the request body the message refers to.

  • No labels