[Resolved] Creating a term translation via REST API with non-unique name

Hi Andreas

I have narrowed down the issue in meantime, and I am not actually sure if this is even a WPML related issue.
Because I couldn't create product categories or tags with custom fields in a single request (whatever data is there just gets ignored during creation), I decided to do 2 requests each time. First using the wpml REST API to create the category/tag including the needed wpml attributes like lang, translationOf etc.
And then a second update request that sets the ACF fields using the wordpress REST API.

Now here is a program flow that fails:
1. Create a tag using the wpml REST API (products/tags)

{
  "name": "Coimbra",
  "description": null,
  "lang": "en",
  "acf": {
    "directus_id": "113",
    "tile_image": null
  },
}

=> Creates tag with id 374 and slug 'coimbra'

2. Update the acf fields using the wordpress REST API (/wp-json/wp/v2/product_tag/374)

{
  acf: {
    "directus_id": "113",
    "tile_image": null
  }
}

=> Works just fine

3. Create a translation (lang: pt) using the wpml REST API (products/tags)

{
  "name": "Coimbra",
  "description": null,
  "lang": "pt",
  "acf": {
    "directus_id": "113",
    "tile_image": null
  },
  "translation_of": 374,
}

=> creates tag with id 375 and slug 'coimbra-2'

4. Update the acf fields using the wordpress REST API (/wp-json/wp/v2/product_tag/375)

{
  acf: {
    "directus_id": "113",
    "tile_image": null
  }
}

=> Fails with the following error:

{
  "code": "duplicate_term_slug",
  "message": "The slug "coimbra-2" is already in use by another term.",
  "data": null
}

The tags are created and are recognized by wpml as translations.
It's just that any update on the translated tag seems to fail with that error, so I am unable to set the acf fields on that tag.

And the error doesn't really make sense to me because the slug that is supposedly duplicated is the one that belongs to the tag I just created and am trying to update...

Best regards
Olivier

I have tried your suggestion and created the slugs in that format. Unfortunately that didn't make any difference.
As a workaround I now ended up just creating a tiny custom REST endpoint that takes my data and uses the 'update_field()' function to set the acf fields.
Thank you nevertheless.

Regards,
Olivier