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

Pylon Accounts API

Customer accounts.

Pylon Accounts API is one of 9 APIs that Pylon publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 8 operations across 4 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.usepylon.com.

8 operations 4 paths 7 schemas 1 DELETE2 GET2 PATCH3 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.usepylon.com
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Pylon Accounts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Pylon API token passed as a Bearer token in the Authorization header. Only Admin users can create API tokens in Pylon settings.

Paths & Operations 8

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

Accounts 8

Customer accounts.

GET
/accounts
List accounts
listAccounts 2 params → 200
POST
/accounts
Create an account
createAccount body → 200
PATCH
/accounts
Update multiple accounts
updateAccounts body → 200
GET
/accounts/{id}
Get an account
getAccount 1 param → 200
PATCH
/accounts/{id}
Update an account
updateAccount 1 param body → 200
DELETE
/accounts/{id}
Delete an account
deleteAccount 1 param → 200
POST
/accounts/search
Search accounts
searchAccounts body → 200
POST
/accounts/merge
Merge accounts
mergeAccounts body → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Account (14 properties), CreateAccountRequest (6 properties), SearchRequest (3 properties), Pagination (2 properties). Each schema is shown below with its type and property counts.

SearchRequest
object
3 properties
AccountListResponse
object
2 properties
NamedRef
object
1 property
Pagination
object
2 properties
AccountResponse
object
1 property
Account
object
14 properties
CreateAccountRequest
object
6 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pylon-accounts-api-openapi.yml Raw ↑

Other APIs Pylon publishes across the network.

Pylon Contacts API
Pylon Custom Fields API
Pylon Issues API
Pylon Knowledge Base API
Pylon Tags API
Pylon Tasks API
Pylon Teams API
Pylon Users API
Where this information came from

This is an independent, third-party profile of Pylon Accounts 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.