...
Create attribute | ||||||||
---|---|---|---|---|---|---|---|---|
Request | POST /editor/attribute | |||||||
Params | termId Required ID of term where attribute should be created, even if not at term-level | |||||||
level=(entry|language|term) Required Level that the attribute should be created for | ||||||||
dataType Required Type of an attribute. Can be integer or string. See filterWindow.attributes[*].(id|type) in Client app setup data response | ||||||||
batch=(0|1) Optional Default 0. If this param is 1, it means that batch-mode is On so termId-param can accept comma-separated term IDs | ||||||||
except=(0|1) Optional Default 0. This param is only applicable when batch-mode is On. Before making request with except=1 you should preliminary run term search request at least once, so the IDs of found terms except given by termId-param would be involved | ||||||||
Batch-mode response example: as you can see, value of Response in case of non-batch-mode would be the same as below, except that:
|
Delete attribute | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Request | DELETE /editor/attribute | |||||||||
Params | attrId Required ID of attribute to be deleted. Can be also be comma-separated list of attribute IDs | |||||||||
|
Provides access to the Term collections available in the application.
...