How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Wish France EPR Compliance API

APIs that support France Extended Producer Responsibility (EPR) Compliance. For a merchant to be compliant with the EPR regulation, a product category they intend to sell must be linked with one or more EPR registration number(s).

Wish France EPR Compliance API is one of 21 APIs that Wish publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include France EPR Compliance. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.

This API exposes 7 operations across 3 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 3.0.65.

Requests are made against a single base URL, https://merchant.wish.com.

7 operations 3 paths 10 schemas 1 DELETE3 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.65
Base URL
https://merchant.wish.com/api/v3
Authentication
OpenID Connect, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Wish France EPR Compliance API declares 2 security schemes for authenticating requests. It supports OpenID Connect (OpenID) discovered at https://merchant.wish.com/oidc/.well-known/openid-configuration. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 37 scopes. By default, every request must be authenticated.

Paths & Operations 7

Across 3 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

France EPR Compliance 7

APIs that support France Extended Producer Responsibility (EPR) Compliance. For a merchant to be compliant with the EPR regulation, a product category they intend to sell must be…

PUT
/api/v3/france_epr_compliance/compliance_status
Bulk update France EPR Product Compliance Status
updateFranceEPRProductComplianceStatus body → 200400
GET
/api/v3/france_epr_compliance/compliance_status
Get France EPR Product Compliance Status
getFranceEPRProductComplianceStatus 5 params → 200400
POST
/api/v3/france_epr_compliance/unique_identification_number
Create a France Product Unique Identification Number
createFranceProductUniqueIdentificationNumber body → 200400
GET
/api/v3/france_epr_compliance/unique_identification_number
List France Product Unique Identification Numbers
listFranceProductUniqueIdentificationNumber → 200400
PUT
/api/v3/france_epr_compliance/unique_identification_number/{id}
Update a France Product Unique Identification Number
updateFranceProductUniqueIdentificationNumber 1 param body → 200400
GET
/api/v3/france_epr_compliance/unique_identification_number/{id}
Get a France Product Unique Identification Number
getFranceProductUniqueIdentificationNumber 1 param → 200400
DELETE
/api/v3/france_epr_compliance/unique_identification_number/{id}
Delete a France Product Unique Identification Number
deleteFranceProductUniqueIdentificationNumber 1 param → 204400

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are FranceProductUniqueIdentificationNumber (3 properties), FranceProductComplianceStatus (3 properties), UpdateFranceProductUniqueIdentificationNumber (2 properties), APIError (2 properties). Each schema is shown below with its type and property counts.

EPRComplianceStatus
string
3 status: (1) a unique identification number linked, (2) no unique identification number, (3) not recommended to link a unique identification number.
FranceProductComplianceStatusResponse
array
List of objects including a product id, compliance status and UIN id.
APIError
object
2 properties 2 required
UpdateFranceProductUniqueIdentificationNumber
object
details of updating a france product unique identification number
2 properties
ListFranceProductUniqueIdentificationNumbersResponse
array
List of France Product Unique Identification Numbers returned
FranceProductComplianceStatus
object
3 properties
FranceProductComplianceStatusRequest
object
2 properties 1 required
FranceProductUniqueIdentificationNumberResponse
a france product unique identification number response
FranceProductUniqueIdentificationNumber
object
details of a france product unique identification number
3 properties
CreateFranceProductUniqueIdentificationNumber
object
details of creating a france product unique identification number

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wish-france-epr-compliance-api-openapi.yml Raw ↑

Other APIs Wish publishes across the network.

Wish Brands API
Wish Bulk Products API
Wish Currencies API
Wish EU Product Compliance API
Wish Germany EPR Compliance API
Wish Merchant API
Wish OAuth API
Wish Orders API
Wish Payments API
Wish Penalties API
Wish ProductBoost API
Wish Products API
Where this information came from

This is an independent, third-party profile of Wish France EPR Compliance API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.