Most Advocate REST API resources accept custom metadata fields in the form of key-value pairs that you can use to store additional information about a resource. For example, you can use custom metadata to store custom external identifiers, tags, or any other information that is relevant to your use case. There are some restrictions that currently apply to custom metadata:
  • The maximum number of custom metadata fields that you can store for a resource is 5.
  • The maximum length of a custom metadata key is 512 characters (UTF-8 encoded).
  • The maximum length of a metadata key is 64 characters (UTF-8 encoded).
  • You can only use letters, digits, underscores and hyphens in the key.
  • The values have to be strings.
  • You can send an empty metadata object.