Product Definition Center

Common Platform Enumeration (CPE) for linking CPE with variants (/rest_api/v1/variant-cpes/).

CPE is a standardized method of describing and identifying classes of operating systems.

Common Vulnerabilities and Exposures (CVE) contain list of affected CPEs.

For more information about CPE see cpe.mitre.org.

Documents & examples

Method: GET

URL: /rest_api/v1/cpes/

Query params:

cpe (string)
description (string)
ordering (string) Comma separated list of fields for ordering results.
- To sort by a field in descending order, prefix its name with minus (e.g. -name).
- Use double underscores for nested field names (e.g. parent__child for {"parent": {"child": ...}}).

Following filters can be used to show only specific fields. This can make response time faster. Format is list or single value (JSON: {"fields": ["a","b"]} or {"fields": "a"}, in URL: ?fields=a&fields=b).

fields (list | string) Fields to display (other fields will be hidden).
exclude_fields: (list | string) Fields NOT to display (overrules fields).

Response: a paged list of following objects

{
    "cpe": "string", 
    "description (optional, default=null)": "string", 
    "id (read-only)": "int"
}

Method: GET

URL: /rest_api/v1/cpes/{instance_pk}/

Response:

{
    "cpe": "string", 
    "description (optional, default=null)": "string", 
    "id (read-only)": "int"
}

Method: POST

URL: /rest_api/v1/cpes/

Data:

{
    "cpe": "string", 
    "description (optional, default=null)": "string"
}

Response:

{
    "cpe": "string", 
    "description (optional, default=null)": "string", 
    "id (read-only)": "int"
}

It is possible to create this resource in bulk. To do so, use the same procedure as when creating a single instance, only the request body should contain a list of JSON objects. The response you get back will also contain a list of values which you would obtain by submitting the request data separately.

Method: PUT, PATCH

URL: /rest_api/v1/cpes/{instance_pk}/

Data:

{
    "cpe": "string", 
    "description (optional, default=null)": "string"
}

Response:

{
    "cpe": "string", 
    "description (optional, default=null)": "string", 
    "id (read-only)": "int"
}

Method: DELETE

URL: /rest_api/v1/cpes/{instance_pk}/

Response:

On success, HTTP status code is 204 and the response has no content.

It is possible to delete multiple items in one request. Use the DELETE method with the same url as for listing/creating objects. The request body should contain a list with identifiers for objects to be deleted. The identifier is usually the last part of the URL for deleting a single object.

It is possible to update multiple objects in one request. Use the PUT or PATCH method with the same url as for listing/creating objects. The request body should contain an object, where keys are identifiers of objects to be modified and their values use the same format as normal update.

Browsable GET

GET /rest_api/v1/cpes/

HTTP 200 OK
Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 0,
    "next": null,
    "previous": null,
    "results": []
}

Cpe List

Documents & examples

Browsable GET