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

Paperless Parts Processes API

Endpoints for managing Processes, Operation Definitions, and Add on Definitions

Paperless Parts Processes API is one of 12 APIs that Paperless Parts publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Processes. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 5 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, {url}/{version}.

5 operations 5 paths 1 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.paperlessparts.com/v2
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Paperless Parts Processes API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (app_id). By default, every request must be authenticated.

  • app_id — API key to authorize requests.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 GET. Each is listed below with its method, path, parameters, and response codes.

Processes 5

Endpoints for managing Processes, Operation Definitions, and Add on Definitions

GET
/processes/public/processes
Get a list of Processes.
ProcessesList → 200404
GET
/processes/public/operation_definitions
Get a list of Operation Defintions.
OperationDefintionList → 200404
GET
/processes/public/discount_definitions
Get a list of Discount definitions.
DiscountDefinitionList → 200404
GET
/processes/public/add_on_definitions
Get a list of Add On Definitions
AddOnDefinitionList → 200404
GET
/processes/public/materials
Get a list of Materials
ListMaterials 5 params → 200404

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

Metadata
object
Object that can be used to attach key-value data to an object. Up to 25 keys can be speficied, with key names up to 40 characters long and values up to 500 cha…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paperless-parts-processes-api-openapi.yml Raw ↑

Other APIs Paperless Parts publishes across the network.

Paperless Parts Contacts API
Paperless Parts Custom Tables API
Paperless Parts Customers API
Paperless Parts Events API
Paperless Parts Integration Actions API
Paperless Parts Jobs API
Paperless Parts Orders API
Paperless Parts Parts API
Paperless Parts Purchased Components API
Paperless Parts Quote Items API
Paperless Parts Quotes API
Where this information came from

This is an independent, third-party profile of Paperless Parts Processes 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.