payabli/integration-skills

payabli-vendors

Use when working with Payabli vendor records — creating, reading, listing or searching, updating, or deleting vendors, or showing a vendor's payment history (an AP directory, vendor portal, or supplier management screen).

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/payabli/integration-skills --skill payabli-vendors

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Payabli vendors

Manage the Pay Out vendor lifecycle: create, read, list/search, update, delete, and payment history.

Load fundamentals first

If payabli-fundamentals is not already loaded, load it now, then continue.

On load

If payabli-integration.md exists at the repo root, read it; honor its ## SDK value.

Vendors are per-paypoint and required before payouts

Vendors are the entities that get paid in Pay Out. Each paypoint keeps its own vendor list — vendors aren't shared across paypoints — and a vendor must exist before you can bill or pay it. Payabli supports US and Canadian vendors only. https://docs.payabli.com/guides/pay-out-developer-vendors-manage.md

Create a vendor

POST /Vendor/single/{entry}. vendorNumber is required and must be unique within the paypoint (a string like VEN-123, not a bare integer). name1 is also required.

Address is all-or-nothing. If you send any address field, the full set (address1, city, state, zip) must be present and valid; the primary address and the remittance address are validated independently. state is checked against country (US states or CA provinces only).

Casing gotcha: requests take lowercase fields (vendorNumber, name1, email, phone, address1). Responses return most fields PascalCase (VendorNumber, Name1, Email, Address1, VendorId), but some stay camelCase (additionalData, customField1, payeeName1, remitAddress1). Vendor status has three forms depending on context — the request field is vendorStatus, the query filter is status, and the response field is VendorStatus. Map case-insensitively rather than assuming one casing.

Read, update, delete

Read one with GET /Vendor/{idVendor}, update with PUT /Vendor/{idVendor}, and delete with DELETE /Vendor/{idVendor}. A vendor's saved payout methods come back on this record as a top-level StoredMethods[] array (each with its IdPmethod — the value you pay as storedMethodId) — there is no separate token-list or Query route for them; see payabli-tokenization.

List and search vendors

GET /Query/vendors/{entry}, or GET /Query/vendors/org/{orgId} for organization-wide results. Filter with fieldName(condition)=value (for example vendorNumber(eq)=VEN-123, name(ct)=supply, status(in)=1|0 — the status filter field is status, not VendorStatus) and paginate with fromRecord/limitRecord. The response wraps results in { Summary, Records }. For the full filter syntax, operators, and exports, use payabli-reporting. https://docs.payabli.com/guides/pay-out-developer-vendors-manage.md

Vendor payment history

To show a vendor's payment history, query the payouts endpoint filtered by vendor: GET /Query/payouts/{entry}?vendorNumber(eq)=... (or vendorId(eq)=...). Each record carries a numeric payout transaction status; decode it from the Pay Out status reference when rendering history.

Vendor enrichment

Payabli can auto-fill vendor payment and contact details from invoices and the web (a beta feature). If a task calls for it, point to the enrichment guide rather than hand-rolling it. https://docs.payabli.com/guides/pay-out-vendor-enrichment-overview.md

Boundaries

  • Creating and sending payouts → payabli-send-payments
  • Bill capture and AP automation → payabli-bills
  • Saving a payout method on a vendor → payabli-tokenization
  • Pay In customers (the customer equivalent of this skill) → payabli-customers
  • Query filter syntax, exports, and reconciliation → payabli-reporting
同じリポジトリから

関連する Skills

すべての Skills
payabli
コミュニティ

payabli-accept-payments

Use when writing code that accepts payments through Payabli: charging cards or ACH, integrating embedded payment components or a hosted payment page, handling Apple Pay or Google Pay, or processing voids and refunds. Boundaries — subscriptions: payabli-subscriptions; invoices and payment links: payabli-invoices; disputes and refund-failure recovery: payabli-disputes. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日
payabli
コミュニティ

payabli-bills

Use when building accounts-payable automation on Payabli — capturing vendor bills (manual entry or OCR) and paying them through Pay Out. Distinct from raw payouts (payabli-send-payments): a bill is a captured vendor invoice that you then pay. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日
payabli
コミュニティ

payabli-boarding

Use when onboarding merchants to Payabli through the API — creating the business, its people, paypoints, and bank accounts, opening a boarding application, validating and submitting it, answering underwriting requests, or tracking an application's status and enablement. Moving an existing integration off the legacy /Boarding/ endpoints lives in payabli-boarding-migration. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日
payabli
コミュニティ

payabli-boarding-migration

Use when moving an existing integration off Payabli's legacy boarding endpoints (/Boarding/app, /Boarding/read, boarding links) to intelligent boarding — converting legacy application payloads to the new records, mapping fields, values, and statuses, or planning the cutover before the legacy sunset. Building boarding from scratch lives in payabli-boarding. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日