Hello,
I found some issues with setting/updating metadata on keys when using the API Import endpoint:
- Adding a limit to an existing key via API seems not to be possible; the new limit is ignored
- Modifying an existing limit via API is ignored
Our tests show that if the key does not exist and the limit is set with the initial import of the new key, then it works as expected, but later changes are ignored.
When trying to update, it does not matter if we send the actual key and its value along or not. The metadata is always ignored unless it is for a new non-existing key.
It might be possible using the API Source Keys Endpoints, but here we can only update one key at a time, resulting in too many requests.
Potential useful info:
we are using an organization token
file type is JSON
language: xxa (Developer English)
And before you ask:
Yes, we use the documented @meta: syntax
Yes, it is on the correct nesting layer
And no, we cannot use the CLI for our purposes