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 Customers API

Paperless Parts includes Customer Relationship Management (CRM) functionality to make it easy to send quotes to new and existing customers, while keeping data consistent with third-party CRM and ERP systems. Typical use cases for these endpoints are to bulk import customers from an existing customer database and to synchronize new customers or changes from another system.An account represents a single company or account to which you would send quotes. An account has zero or more Contacts, each of which represents a person at that company and is identified uniquely by their email address. An account also has facilities and billing addresses. Facilities represent destinations to which orders can be shipped and BillingAddresses represent the bill to address for and order.

Paperless Parts Customers 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 Customers. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 17 operations across 9 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

17 operations 9 paths 10 schemas 9 GET4 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Paperless Parts Customers 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 17

Across 9 paths, the API surfaces 17 operations — 9 GET, 4 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Customers 17

Paperless Parts includes Customer Relationship Management (CRM) functionality to make it easy to send quotes to new and existing customers, while keeping data consistent with thir…

GET
/contacts/public
List contacts
ListContacts 3 params → 200404
POST
/contacts/public
Create new contact
CreateContact body → 201
GET
/contacts/public/{contactId}
Get details about a Contact
ContactDetails 1 param → 200
PATCH
/contacts/public/{contactId}
Update a Contact
UpdateCustomer 1 param body → 200
GET
/accounts/public
List accounts
ListAccounts 4 params → 200404
POST
/accounts/public
Create new Account
CreateAccoumt body → 201
GET
/accounts/public/{accountId}
Get details about an Account
AccountDetails 1 param → 200404
PATCH
/accounts/public/{accountId}
Update an Account
UpdateCompany 1 param body → 200
GET
/accounts/public/{accountId}/billing_addresses
List account billing addresses
ListBillingAddresses 1 param → 200404
POST
/accounts/public/{accountId}/billing_addresses
Create a new billing address for an account
CreateBillingAddress 1 param body → 201
GET
/accounts/public/{accountId}/facilities
List account facilites
ListFacilities 1 param → 200404
POST
/accounts/public/{accountId}/facilities
Create a new facility for an account
CreateFacility 1 param body → 201
GET
/billing_addresses/public/{billingAddressId}
Get Billing Address
BillingAddress 1 param → 200404
PATCH
/billing_addresses/public/{billingAddressId}
Update a Billing Address
UpdateBillingAddress 1 param body → 200
GET
/facilities/public/{facilityId}
Get A Facility
Facility 1 param → 200404
PATCH
/facilities/public/{facilityId}
Update a Facility
UpdateFacility 1 param body → 200
GET
/customers/public/payment_terms
Returns a list of payment terms
ListPaymentTerms → 200404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Account (21 properties), Contact (13 properties), Address (8 properties), Facility (6 properties). Each schema is shown below with its type and property counts.

Address
object
8 properties
BillingAddressId
integer
The billing address id
BillingAddress
FacilityId
integer
The facility id
Facility
objectnull
6 properties
Contact
object
13 properties
SalesPerson
object
5 properties
Account
object
21 properties
CustomerId
integer
The customer id
AccountId
integer
The account id

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Paperless Parts publishes across the network.

Paperless Parts Contacts API
Paperless Parts Custom Tables API
Paperless Parts Events API
Paperless Parts Integration Actions API
Paperless Parts Jobs API
Paperless Parts Orders API
Paperless Parts Parts API
Paperless Parts Processes 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 Customers 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.