PrestaShop API error messages

Tip

This guide references the error messages that Ciklik may return during interaction with the PrestaShop API (cart creation, product addition, combination management, etc.).

Prerequisites

• Knowledge of PrestaShop architecture (products, combinations, carts)
• Access to PrestaShop and Ciklik back offices
• Familiarity with PrestaShop id_product and id_product_attribute concepts

Error message reference

Error message	PrestaShop context	Recommended action
Missing parameter : id	Missing ID parameter in the request to PrestaShop	Check the subscription integrity in Ciklik and consistency with the PrestaShop catalog
Bad parameter : id	Invalid ID parameter — the combination or product has been deleted/modified in the PrestaShop back office	Recreate the combination or update the subscription product
Cart not found	The referenced PrestaShop cart no longer exists	Regenerate the cart (issue often related to database cleanup on the PrestaShop side)
Missing parameter : id_product_attribute	PrestaShop combination not specified	The product configured in the subscription requires a combination (size, color, packaging, etc.)

Most common error: Bad parameter : id

Common pitfall — PrestaShop combination deletion

This is the #1 cause of recurring rebill errors.

If a merchant deletes a combination (id_product_attribute) in their PrestaShop back office while subscriptions reference it, all affected rebills will systematically fail with the Bad parameter : id error.

Typical scenario

1. The merchant creates a “Coffee 250g” product with two combinations:

   • Ground (id_product_attribute = 42)
   • Whole bean (id_product_attribute = 43)

2. Customers subscribe to the “Ground” combination (id = 42)

3. The merchant decides to reorganize their catalog and deletes the “Ground” combination to recreate it differently

4. The new “Ground” combination now has id = 87

5. Result: All subscriptions that referenced id 42 fail with Bad parameter : id

Solutions

The subscription will no longer be able to renew until one of these actions is performed:

Option 1: Recreate the combination with the same ID (complex)

• Requires intervention in the PrestaShop database
• Not recommended as it is risky

Option 2: Update the subscription product on the Ciklik side (recommended)

• Via the Ciklik back office: Modify a subscription product
• Or via the Ciklik API for bulk modifications

Best practice

Before deleting any combination in PrestaShop, verify that no active subscription references it.

Use the Ciklik API to filter subscriptions by product:

GET /api/subscriptions?filter[product_id]=42&filter[status]=active

Cart not found error

This error occurs when the PrestaShop cart referenced by Ciklik no longer exists.

Possible causes

• Automatic cart cleanup: PrestaShop deletes abandoned carts by default after a certain period. If a rebill is delayed (server unavailability, etc.), the initial cart may have been deleted.

• Manual database purge: Cleanup of ps_cart and ps_cart_product tables without precaution.

• Maintenance module: Some PrestaShop cleanup modules delete “orphan” carts.

Solution

The rebill will be automatically retried with the creation of a new cart. If the error persists, check the automatic cart cleanup configuration in PrestaShop.

Missing parameter : id_product_attribute error

This error indicates that the product configured in the subscription has required combinations, but no combination was specified.

Possible causes

• The subscription was created before combinations were added to the product
• Incomplete data migration
• Bug during subscription creation

Solution

Update the subscription to specify the desired combination via Modify a subscription product.

Diagnosis and resolution

Step 1: Identify subscriptions with errors

Via the rebill-errors API:

GET /api/rebill-errors?filter[created_at_after]=2026-01-01

Step 2: Analyze the error message

Refer to the reference table above to understand the cause.

Step 3: Verify catalog consistency

Compare:

• The product/combination ID stored in the Ciklik subscription
• The existence of this ID in the PrestaShop catalog

Step 4: Correct

Depending on the diagnosis:

• Update the subscription product
• Recreate the missing elements in PrestaShop
• Contact Ciklik support for complex cases

FAQ

Q: How do I identify all subscriptions affected by a combination deletion?

Filter active subscriptions by the relevant combination ID via the API:

GET /api/subscriptions?filter[id_product_attribute]=42&filter[status]=active

Q: Can I bulk modify subscription products?

Yes, via the Ciklik API. Contact support for assistance with bulk modifications.

Q: Are these errors visible in the PrestaShop back office?

No, these errors are captured by Ciklik before reaching PrestaShop. They are only visible in the Ciklik back office or via the rebill-errors API.