API ACCESS / INTEGRATIONS / COST
Before you build an integration
How do you get Pylon API access?
A Pylon Admin creates a token in Settings, Integrations & dev, API tokens. Give the integration a dedicated identity with the least sufficient role and use the tenant’s US or EU API region. Tokens have no independent scopes and do not expire; rotating one immediately invalidates its old value. Deactivating the Admin who created a token can also revoke it.
Is the Pylon API free?
REST API and webhooks are included in Professional, the lowest listed paid plan at $89 per seat on an annual contract. Advanced is listed at $139 per seat on an annual contract and adds Data warehouse. No separate fixed API fee is stated on the comparison, but a paid subscription and customer order terms still apply. Warehouse destination costs are separate.
Can the Pylon API write data?
Yes. Issue and account APIs expose create and update, while message endpoints support customer replies and internal notes. The token’s role controls access. Deletes and channel-visible message edits have wider consequences; an uncertain create or send must be reconciled before retry because no universal idempotency key was established.
Which Pylon integration route should you use?
Choose the REST API when your application needs both operational reads and writes. Use warehouse delivery when an eligible customer wants recurring analytical data in its own destination. S3 receives a full selected-schema Parquet dataset each run, so process the newest complete partition as a replacement snapshot. A warehouse read route does not provide writes back to Pylon.
Can a chosen third party hold a Pylon API token?
The reviewed documents do not settle this. Admin-created API tokens support integrations, but Terms 1.4 restrict sharing account access credentials with third parties while section 1.6 describes compatible Third-Party Services. Confirm that a dedicated integration token may be held by your chosen provider before relying on that hosted route. Public OAuth onboarding and an approval SLA were not established.
How do you keep a Pylon copy up to date?
Use issue updated_at search with overlap and ID deduplication to revisit changed surviving issues. The ordinary list filters creation time, so using that timestamp alone misses edits to old issues. Full collection refreshes can rebuild current state. Webhooks have bounded retries and no ordering guarantee; retained delete identities, historical replay and child-message watermark behavior still require validation.
Can you export Pylon data and leave?
API records and eligible warehouse delivery provide usable copies while access is active. Full product migration still needs checks for file bytes, deleted records, past versions and configuration. The termination terms do not establish a defined retrieval window after cancellation. Native triggers (even when customer-authored) have no verified independent export-and-execution path in the reviewed documentation.
API guide checked 2026-10-23. Scoring evidence keeps its own dates below.
OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Current issues, accounts and users have structured REST responses within the declared support-product scope.
Pylon issues API ↗
Get a list of issues; Get an issue · Checked 2026-10-23
Bulk delivery 8.8/10
Batched or iterable API requests
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Issue lists and search support cursor traversal. Higher-plan warehouse delivery is excluded from this API anchor.
Pylon API conventions ↗
Pagination; Listing issues by time · Checked 2026-10-23
Query expressiveness 8.8/10
Documented structured API filters
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Issue search accepts structured predicates, including updated_at time ranges and grouped conditions.
Pylon issues API ↗
Search for issues by a given filter · Checked 2026-10-23
Access cost barrier 10.0/10
Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligible
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
The lowest listed paid plan, Professional, includes REST API; Advanced warehouse delivery is outside this API assessment.
Pylon published plans and developer platform ↗
Seats; Developer platform: REST API · Checked 2026-10-23
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Admin token creation is documented, but Terms 1.4 restrict third-party credential sharing. Dedicated hosted-integration token eligibility remains unresolved.
Pylon Terms of Service ↗
1.4 Authorized Users; 1.6 Third-Party Services · Checked 2026-10-23
Downstream permission -
-
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Customer Data ownership and compatible integrations are described; permission for this hosted third-party token and processing arrangement still needs confirmation.
Pylon Terms of Service ↗
1.4 Authorized Users; 1.6 Third-Party Services; 3.2 Customer Data · Checked 2026-10-23
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Issue and account APIs document create/update in the assessed support product; customer replies and internal notes are separate operational actions.
Pylon issues API ↗
Create a new issue; Update an existing issue · Checked 2026-10-23
Pylon accounts API ↗
Create a new account; Update an existing account · Checked 2026-10-23
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Admins create tokens for customer-run API applications; this does not settle independent third-party token custody.
Pylon API authentication and regions ↗
Create an API token · Checked 2026-10-23
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
POST /issues/search supports updated_at time_range polling. GET /issues filters created_at.
Pylon issues API ↗
Search for issues by a given filter; Get a list of issues · Checked 2026-10-23
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Numeric per-endpoint organization quotas and 429 recovery headers are documented.
Pylon API rate limits ↗
How limits apply; Response headers; Handling 429 responses · Checked 2026-10-23
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Issue search exposes updated_at. Permanent issue deletion exists, but no retained deletion identity stream was established.
Pylon issues API ↗
Search for issues by a given filter; Delete an existing issue · Checked 2026-10-23
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Overlapping updated-time queries can re-fetch surviving changed issues. Retained intermediate versions and durable replay checkpoints are not documented.
Pylon API conventions ↗
Listing issues by time; Search filters · Checked 2026-10-23
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Customers can retain structured issue records from authorized list/search responses.
Pylon issues API ↗
Get a list of issues; Search for issues by a given filter · Checked 2026-10-23
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Terms end service rights on termination and provide deletion on written request; no defined customer retrieval window or exit-charge promise was found.
Pylon Terms of Service ↗
5.4 Effect of Termination · Checked 2026-10-23
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Portable current issue records are documented; whole-product history, attachment completeness and native restore remain unverified.
Pylon issues API ↗
Get a list of issues; Get an issue · Checked 2026-10-23
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 5.0/10
Customer-editable native workflows or agent configurations
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Customers create native triggers with events, conditions and actions, from templates or from scratch.
Pylon native workflow triggers ↗
Setup · Checked 2026-10-23
Rights to custom logic -
-
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Customer Data and Pylon technology rights are distinguished; ownership/export/external execution of customer-authored native triggers is not established.
Pylon Terms of Service ↗
3.2 Customer Data; 3.4 Pylon Rights · Checked 2026-10-23
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Admins create dedicated API tokens in Settings, Integrations & dev, API tokens. Each token has its own identity and role or acts as a selected teammate or bot; its current role controls access. Tokens have no separate scopes and do not expire. Rotation invalidates the old value immediately, and deactivating a creator can revoke integration tokens. Match the US or EU API to the tenant and configure any IP allowlist. The terms prohibit sharing account access credentials with third parties but also describe compatible integrations, leaving custody of a dedicated integration token unresolved.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Use the REST API for selected current issues, accounts, contacts and users; messages include internal notes and require a deliberate coverage decision. Cursor pagination supports repeatable collection traversal, and custom-field metadata identifies API slugs. Advanced and Enterprise add warehouse delivery to Snowflake, BigQuery, Redshift or S3. The S3 integration writes the entire selected-schema dataset as Parquet in its latest partition on every run. This is a separate customer destination route; warehouse entitlement does not grant API write access or establish complete product history.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-run role-bearing API token | API key | Customer | Not confirmed | professional includes rest api. admin creates a role-bearing token for the tenant region. customer-run access is documented; permute custody needs confirmation against terms 1.4 credential-sharing restrictions. | 2026-10-23 |
| Customer S3 warehouse delivery | IAM role | Customer | No | advanced or enterprise warehouse entitlement; customer creates destination role/policy for pylon and enables the s3 app. each run writes a full selected-schema parquet partition; permute reads that bucket under a separate customer grant. | 2026-10-23 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Professional lists $89 per seat on an annual contract and includes REST API and webhooks. Advanced lists $139 per seat on an annual contract and adds Data warehouse; Enterprise uses a custom quote. The published comparison states no separate fixed API fee, so an existing Professional customer has no listed API-tier upgrade. This is included access within a paid subscription, with customer order terms still governing charges. Destination infrastructure costs are separate. Neither the pricing page nor token creation establishes permission for a third party to hold credentials.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The API documents creating and updating issues and accounts, including issue assignment, status and custom-field changes. It can also send customer-visible replies and add internal notes. Message editing is limited by author, message type and current permissions; edits can propagate to the connected channel. Permanent deletion is a separate destructive operation. PATCH changes supplied fields, while arrays can replace full lists; bulk issue updates can skip missing or inaccessible records. No universal idempotency-key contract was established, so an uncertain create or send needs reconciliation before retrying.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
POST /issues/search supports updated_at filters, including overlapping time ranges that can revisit changed surviving records. GET /issues filters created_at and would miss later edits to older issues if used as the only incremental watermark. Accounts and contacts do not expose an equivalent built-in update-time search filter in the reviewed field lists. Quotas are shared across organization tokens per endpoint, with numeric limits and Retry-After recovery. Signed trigger webhooks have three total attempts and no ordering guarantee. They can prompt a refetch, but do not establish durable replay, deletion recovery or propagation of every child-message edit to the parent issue watermark.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Issue search exposes updated_at. Permanent issue deletion exists, but no retained deletion identity stream was established. | Pylon issues API ↗Search for issues by a given filter; Delete an existing issueChecked 2026-10-23 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Overlapping updated-time queries can re-fetch surviving changed issues. Retained intermediate versions and durable replay checkpoints are not documented. | Pylon API conventions ↗Listing issues by time; Search filtersChecked 2026-10-23 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Authorized API responses provide portable current records. Eligible customers can retain selected warehouse data in their own destination; S3 publishes full Parquet snapshots rather than an event history. A migration still needs a coverage check for attachments, historical changes, relationships and native configuration. Attachment URLs can be sensitive and are not the same as a verified archive of file bytes. The terms end service rights on termination and describe deletion after written request; they do not establish a defined post-cancellation retrieval window or a complete restoration package. Plan extraction while access is active.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers build Pylon triggers from events, conditions and actions, starting from templates or from scratch. Those native workflows can call external webhooks (whose delivery still needs recovery handling) and use selected object fields. The reviewed sources distinguish Customer Data rights from Pylon technology rights, but do not establish reusable export or independent execution rights for customer-authored trigger definitions. Owning external API integration code does not establish portability of the native workflow.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Current issues, accounts and users have structured REST responses within the declared support-product scope. | Pylon issues API ↗Get a list of issues; Get an issueChecked 2026-10-23 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Issue lists and search support cursor traversal. Higher-plan warehouse delivery is excluded from this API anchor. | Pylon API conventions ↗Pagination; Listing issues by timeChecked 2026-10-23 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Issue search accepts structured predicates, including updated_at time ranges and grouped conditions. | Pylon issues API ↗Search for issues by a given filterChecked 2026-10-23 |
| Who decides whether a chosen third party may connect? | -Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Admin token creation is documented, but Terms 1.4 restrict third-party credential sharing. Dedicated hosted-integration token eligibility remains unresolved. | Pylon Terms of Service ↗1.4 Authorized Users; 1.6 Third-Party ServicesChecked 2026-10-23 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligibleCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. The lowest listed paid plan, Professional, includes REST API; Advanced warehouse delivery is outside this API assessment. | Pylon published plans and developer platform ↗Seats; Developer platform: REST APIChecked 2026-10-23 |
| What permission is needed for the documented downstream use? | -Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Customer Data ownership and compatible integrations are described; permission for this hosted third-party token and processing arrangement still needs confirmation. | Pylon Terms of Service ↗1.4 Authorized Users; 1.6 Third-Party Services; 3.2 Customer DataChecked 2026-10-23 |
| Which external write operations are documented? | Create and update in one business domainCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Issue and account APIs document create/update in the assessed support product; customer replies and internal notes are separate operational actions. | Pylon issues API ↗Create a new issue; Update an existing issueChecked 2026-10-23 Pylon accounts API ↗Create a new account; Update an existing accountChecked 2026-10-23 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Admins create tokens for customer-run API applications; this does not settle independent third-party token custody. | Pylon API authentication and regions ↗Create an API tokenChecked 2026-10-23 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. POST /issues/search supports updated_at time_range polling. GET /issues filters created_at. | Pylon issues API ↗Search for issues by a given filter; Get a list of issuesChecked 2026-10-23 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Numeric per-endpoint organization quotas and 429 recovery headers are documented. | Pylon API rate limits ↗How limits apply; Response headers; Handling 429 responsesChecked 2026-10-23 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Customers can retain structured issue records from authorized list/search responses. | Pylon issues API ↗Get a list of issues; Search for issues by a given filterChecked 2026-10-23 |
| What retrieval rights are documented at cancellation? | -Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Terms end service rights on termination and provide deletion on written request; no defined customer retrieval window or exit-charge promise was found. | Pylon Terms of Service ↗5.4 Effect of TerminationChecked 2026-10-23 |
| How can customers define their own business logic? | Customer-editable native workflows or agent configurationsCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Customers create native triggers with events, conditions and actions, from templates or from scratch. | Pylon native workflow triggers ↗SetupChecked 2026-10-23 |
| What rights or portability are documented for custom workflow artifacts? | -Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Customer Data and Pylon technology rights are distinguished; ownership/export/external execution of customer-authored native triggers is not established. | Pylon Terms of Service ↗3.2 Customer Data; 3.4 Pylon RightsChecked 2026-10-23 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedCustomer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. Portable current issue records are documented; whole-product history, attachment completeness and native restore remain unverified. | Pylon issues API ↗Get a list of issues; Get an issueChecked 2026-10-23 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Whether Permute may hold customer-created integration tokens under the credential-sharing clause
- Complete hard-delete, merge and message-edit recovery after missed changes
- Attachment, historical and native-configuration completeness; post-cancellation retrieval rights
- Customer-specific API/warehouse fees and native workflow portability rights
Documentation
Assessment checked 2026-10-23. Each answer retains its source and applicable route; the check date does not establish live account behavior.