Perso REST: ezp -> ibexa

[reithor]

PR Fixes wrong namings (REST API)
See https://github.com/ibexa/personalization/blob/main/src/bundle/Resources/config/routing_rest.yaml for correct REST routes

Section about contenttypes endpoint needs to reevaluated - the endpoint does not exist in current release!

Checklist

• Text renders correctly
• Text has been checked with vale
• Description metadata is up to date
• Redirects cover removed/moved pages
• Code samples are working
• PHP code samples have been fixed with PHP CS fixer
• Added link to this PR in relevant JIRA ticket or code PR

[reithor]

Hi @ciastektk ,
Docs mention a contenttypes endpoint for the REST API (see
https://doc.ibexa.co/en/latest/personalization/enable_personalization/#check-whether-the-bundle-provides-rest-data) - which is not defined in https://github.com/ibexa/personalization/blob/main/src/bundle/Resources/config/routing_rest.yaml.

Was the endpoint removed at some point or is /personalization/v1/content/list/{contentIds} a replacement ?

[mnocon]

Thank you!

[mnocon]

@reithor About:

Hi @ciastektk , Docs mention a contenttypes endpoint for the REST API (see https://doc.ibexa.co/en/latest/personalization/enable_personalization/#check-whether-the-bundle-provides-rest-data) - which is not defined in https://github.com/ibexa/personalization/blob/main/src/bundle/Resources/config/routing_rest.yaml.

Was the endpoint removed at some point or is /personalization/v1/content/list/{contentIds} a replacement ?

I see these endpoint was removed in ezsystems/ezrecommendation-client#102 (cross-merged in https://github.com/ibexa/personalization/pull/117) and there is no replacement mentioned - it's described as useless code.

Could you please remove mentions of this endpoint and then we could merge this?

[reithor]

@mnocon @nkostiv :
changes:

• details about token authorization
• the export command part (export command always needs siteaccess, customer-id and license-key)
• added information about where exported files ares stored locally (see also: Update enable_personalization.md #2499)

[adriendupuis]

Preview: https://ez-systems-developer-documentation--2346.com.readthedocs.build/en/2346/personalization/enable_personalization/#check-whether-the-bundle-provides-rest-data

Thank you @reithor for the update and enhencement.

I'm not sure about the examples using curl format instead of HTTP format. I would have fix and update the HTTP request examples. At list, the new curl example is correct while previous HTTP syntax was wrong (wrong regarding HTTP syntax even before being outdated regarding perso REST).

[adriendupuis]

Suggested change

	```
	```bash

[adriendupuis]

Suggested change

	```
	```bash

[adriendupuis]

Suggested change

	curl --location '{PERSONALIZATION_HOST_URI}/api/ibexa/v2/personalization/v1/contentlist/{comma_separated_content_ids}?lang={comma_separated_languages}' \
	--header 'Accept: application/vnd.ibexa.api.ContentList+json' \
	--header 'Authorization: Bearer {BEARER_TOKEN}'
	```
	curl --location '{PERSONALIZATION_HOST_URI}/api/ibexa/v2/personalization/v1/contentlist/{comma_separated_content_ids}?lang={comma_separated_languages}' \
	--header 'Accept: application/vnd.ibexa.api.ContentList+json' \
	--header 'Authorization: Bearer {BEARER_TOKEN}'
	```