@paygentic/sdk
v0.6.4
Published
Developer-friendly & type-safe Typescript SDK specifically catered to leverage *paygentic* API.
Keywords
Readme
paygentic
Developer-friendly & type-safe Typescript SDK specifically catered to leverage paygentic API.
Summary
Paygentic API: The Paygentic API provides a comprehensive platform for building and scaling monetization infrastructure.
Authentication
All API requests require authentication using an API key passed in the Authorization header:
Authorization: Bearer YOUR_API_KEYBase URL
All API requests should be made to:
https://api.paygentic.io/v0Table of Contents
SDK Installation
The SDK can be installed with either npm, pnpm, bun or yarn package managers.
NPM
npm add @paygentic/sdkPNPM
pnpm add @paygentic/sdkBun
bun add @paygentic/sdkYarn
yarn add @paygentic/sdk[!NOTE] This package is published with CommonJS and ES Modules (ESM) support.
Requirements
For supported JavaScript runtimes, please consult RUNTIMES.md.
SDK Example Usage
Example
import { Paygentic } from "@paygentic/sdk";
const paygentic = new Paygentic({
bearerAuth: process.env["PAYGENTIC_BEARER_AUTH"] ?? "",
});
async function run() {
const result = await paygentic.billableMetrics.createBillableMetric({
aggregation: "SUM",
description: "other gracefully hold",
merchantId: "<id>",
name: "<value>",
productId: "<id>",
unit: "becquerel",
});
console.log(result);
}
run();
Authentication
Per-Client Security Schemes
This SDK supports the following security scheme globally:
| Name | Type | Scheme | Environment Variable |
| ------------ | ---- | ----------- | ----------------------- |
| bearerAuth | http | HTTP Bearer | PAYGENTIC_BEARER_AUTH |
To authenticate with the API the bearerAuth parameter must be set when initializing the SDK client instance. For example:
import { Paygentic } from "@paygentic/sdk";
const paygentic = new Paygentic({
bearerAuth: process.env["PAYGENTIC_BEARER_AUTH"] ?? "",
});
async function run() {
const result = await paygentic.billableMetrics.createBillableMetric({
aggregation: "SUM",
description: "other gracefully hold",
merchantId: "<id>",
name: "<value>",
productId: "<id>",
unit: "becquerel",
});
console.log(result);
}
run();
Available Resources and Operations
BillableMetrics
- createBillableMetric - Create
- listBillableMetrics - List
- getBillableMetric - Get
- updateBillableMetric - Update
Customers
- listCustomers - List by Merchant
- createCustomer - Create
- getCustomer - Get
- updateCustomer - Update
Disputes
- createDispute - Create
- listDisputes - List
Entitlements
- getActiveEntitlements - List by Customer
- createEntitlement - Create
- listEntitlements - List Entitlements
Features
- listFeatures - List
- createFeature - Create
- getFeature - Get
- updateFeature - Update
- deleteFeature - Delete
Fees
- createFee - Create
- listFees - List
- getFee - Get
- updateFee - Update
- deleteFee - Delete
- getFeePrice - Get Fee Price
InvoicesV2
- listInvoices - List
- getInvoice - Get
- getInvoiceLineItems - Get Line Items
Plans
- createPlan - Create
- listPlans - List
- listAvailablePlans - List Available Plans
- getPlan - Get
- updatePlan - Update
Prices
- createPrice - Create
- listPrices - List
- getPrice - Get
- updatePrice - Update
- deletePrice - Delete
Products
- createProduct - Create
- listProducts - List
- getProduct - Get
- updateProduct - Update
Revenue
- getRevenue - Get revenue time series
Sources
- createSource - Create
- listSources - List
- getSource - Get
- updateSource - Update
- listSourceEvents - List Events
- approveSourceEvent - Approve
- rejectSourceEvent - Reject
- bulkApproveSourceEvents - Bulk Approve
- bulkRejectSourceEvents - Bulk Reject
- listSourceRules - List Rules
- createSourceRule - Create Rule
- getSourceRule - Get Rule
- updateSourceRule - Update Rule
- deleteSourceRule - Delete Rule
Subscriptions
- listSubscriptions - List
- createSubscription - Create
- getSubscription - Get
- generatePortalLink - Generate Portal Link
- terminateSubscription - Terminate
TestClocks
- listTestClocks - List
- createTestClock - Create
- getTestClock - Get
- advanceTestClock - Advance
- deleteTestClock - Delete
UsageEvents
- createUsageEvent - Create
- listUsageEvents - List
- getUsageEvent - Get
- refundUsageEvent - Refund
- batchCreateUsageEvents - Batch Create
Users
- getUser - Get
- updateUser - Update
Standalone functions
All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.
To read more about standalone functions, check FUNCTIONS.md.
billableMetricsCreateBillableMetric- CreatebillableMetricsGetBillableMetric- GetbillableMetricsListBillableMetrics- ListbillableMetricsUpdateBillableMetric- UpdatecustomersCreateCustomer- CreatecustomersGetCustomer- GetcustomersListCustomers- List by MerchantcustomersUpdateCustomer- UpdatedisputesCreateDispute- CreatedisputesListDisputes- ListentitlementsCreateEntitlement- CreateentitlementsGetActiveEntitlements- List by CustomerentitlementsListEntitlements- List EntitlementsfeaturesCreateFeature- CreatefeaturesDeleteFeature- DeletefeaturesGetFeature- GetfeaturesListFeatures- ListfeaturesUpdateFeature- UpdatefeesCreateFee- CreatefeesDeleteFee- DeletefeesGetFee- GetfeesGetFeePrice- Get Fee PricefeesListFees- ListfeesUpdateFee- UpdateinvoicesV2GetInvoice- GetinvoicesV2GetInvoiceLineItems- Get Line ItemsinvoicesV2ListInvoices- ListplansCreatePlan- CreateplansGetPlan- GetplansListAvailablePlans- List Available PlansplansListPlans- ListplansUpdatePlan- UpdatepricesCreatePrice- CreatepricesDeletePrice- DeletepricesGetPrice- GetpricesListPrices- ListpricesUpdatePrice- UpdateproductsCreateProduct- CreateproductsGetProduct- GetproductsListProducts- ListproductsUpdateProduct- UpdaterevenueGetRevenue- Get revenue time seriessourcesApproveSourceEvent- ApprovesourcesBulkApproveSourceEvents- Bulk ApprovesourcesBulkRejectSourceEvents- Bulk RejectsourcesCreateSource- CreatesourcesCreateSourceRule- Create RulesourcesDeleteSourceRule- Delete RulesourcesGetSource- GetsourcesGetSourceRule- Get RulesourcesListSourceEvents- List EventssourcesListSourceRules- List RulessourcesListSources- ListsourcesRejectSourceEvent- RejectsourcesUpdateSource- UpdatesourcesUpdateSourceRule- Update RulesubscriptionsCreateSubscription- CreatesubscriptionsGeneratePortalLink- Generate Portal LinksubscriptionsGetSubscription- GetsubscriptionsListSubscriptions- ListsubscriptionsTerminateSubscription- TerminatetestClocksAdvanceTestClock- AdvancetestClocksCreateTestClock- CreatetestClocksDeleteTestClock- DeletetestClocksGetTestClock- GettestClocksListTestClocks- ListusageEventsBatchCreateUsageEvents- Batch CreateusageEventsCreateUsageEvent- CreateusageEventsGetUsageEvent- GetusageEventsListUsageEvents- ListusageEventsRefundUsageEvent- RefundusersGetUser- GetusersUpdateUser- Update
Retries
Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.
To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:
import { Paygentic } from "@paygentic/sdk";
const paygentic = new Paygentic({
bearerAuth: process.env["PAYGENTIC_BEARER_AUTH"] ?? "",
});
async function run() {
const result = await paygentic.billableMetrics.createBillableMetric({
aggregation: "SUM",
description: "other gracefully hold",
merchantId: "<id>",
name: "<value>",
productId: "<id>",
unit: "becquerel",
}, {
retries: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
});
console.log(result);
}
run();
If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:
import { Paygentic } from "@paygentic/sdk";
const paygentic = new Paygentic({
retryConfig: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
bearerAuth: process.env["PAYGENTIC_BEARER_AUTH"] ?? "",
});
async function run() {
const result = await paygentic.billableMetrics.createBillableMetric({
aggregation: "SUM",
description: "other gracefully hold",
merchantId: "<id>",
name: "<value>",
productId: "<id>",
unit: "becquerel",
});
console.log(result);
}
run();
Error Handling
PaygenticError is the base class for all HTTP error responses. It has the following properties:
| Property | Type | Description |
| ------------------- | ---------- | --------------------------------------------------------------------------------------- |
| error.message | string | Error message |
| error.statusCode | number | HTTP response status code eg 404 |
| error.headers | Headers | HTTP response headers |
| error.body | string | HTTP body. Can be empty string if no body is returned. |
| error.rawResponse | Response | Raw HTTP response |
| error.data$ | | Optional. Some errors may contain structured data. See Error Classes. |
Example
import { Paygentic } from "@paygentic/sdk";
import * as errors from "@paygentic/sdk/models/errors";
const paygentic = new Paygentic({
bearerAuth: process.env["PAYGENTIC_BEARER_AUTH"] ?? "",
});
async function run() {
try {
const result = await paygentic.billableMetrics.createBillableMetric({
aggregation: "SUM",
description: "other gracefully hold",
merchantId: "<id>",
name: "<value>",
productId: "<id>",
unit: "becquerel",
});
console.log(result);
} catch (error) {
// The base class for HTTP error responses
if (error instanceof errors.PaygenticError) {
console.log(error.message);
console.log(error.statusCode);
console.log(error.body);
console.log(error.headers);
// Depending on the method different errors may be thrown
if (error instanceof errors.ErrorT) {
console.log(error.data$.error); // string
console.log(error.data$.message); // string
console.log(error.data$.details); // { [k: string]: any }
}
}
}
}
run();
Error Classes
Primary errors:
PaygenticError: The base class for HTTP error responses.ErrorT: Generic error.
Network errors:
ConnectionError: HTTP client was unable to make a request to a server.RequestTimeoutError: HTTP request timed out due to an AbortSignal signal.RequestAbortedError: HTTP request was aborted by the client.InvalidRequestError: Any input used to create a request is invalid.UnexpectedClientError: Unrecognised or unexpected error.
Inherit from PaygenticError:
ValidationError: Bad Request - The request could not be understood or was missing required parameters. Status code400. Applicable to 43 of 73 methods.*ConflictError: Fee cannot be deleted because it has associated prices. Status code409. Applicable to 1 of 73 methods.*ResponseValidationError: Type mismatch between the data returned from the server and the structure expected by the SDK. Seeerror.rawValuefor the raw value anderror.pretty()for a nicely formatted multi-line string.
* Check the method documentation to see if the error is applicable.
Server Selection
Override Server URL Per-Client
The default server can be overridden globally by passing a URL to the serverURL: string optional parameter when initializing the SDK client instance. For example:
import { Paygentic } from "@paygentic/sdk";
const paygentic = new Paygentic({
serverURL: "https://api.paygentic.io",
bearerAuth: process.env["PAYGENTIC_BEARER_AUTH"] ?? "",
});
async function run() {
const result = await paygentic.billableMetrics.createBillableMetric({
aggregation: "SUM",
description: "other gracefully hold",
merchantId: "<id>",
name: "<value>",
productId: "<id>",
unit: "becquerel",
});
console.log(result);
}
run();
Custom HTTP Client
The TypeScript SDK makes API calls using an HTTPClient that wraps the native
Fetch API. This
client is a thin wrapper around fetch and provides the ability to attach hooks
around the request lifecycle that can be used to modify the request or handle
errors and response.
The HTTPClient constructor takes an optional fetcher argument that can be
used to integrate a third-party HTTP client or when writing tests to mock out
the HTTP client and feed in fixtures.
The following example shows how to:
- route requests through a proxy server using undici's ProxyAgent
- use the
"beforeRequest"hook to add a custom header and a timeout to requests - use the
"requestError"hook to log errors
import { Paygentic } from "@paygentic/sdk";
import { ProxyAgent } from "undici";
import { HTTPClient } from "@paygentic/sdk/lib/http";
const dispatcher = new ProxyAgent("http://proxy.example.com:8080");
const httpClient = new HTTPClient({
// 'fetcher' takes a function that has the same signature as native 'fetch'.
fetcher: (input, init) =>
// 'dispatcher' is specific to undici and not part of the standard Fetch API.
fetch(input, { ...init, dispatcher } as RequestInit),
});
httpClient.addHook("beforeRequest", (request) => {
const nextRequest = new Request(request, {
signal: request.signal || AbortSignal.timeout(5000)
});
nextRequest.headers.set("x-custom-header", "custom value");
return nextRequest;
});
httpClient.addHook("requestError", (error, request) => {
console.group("Request Error");
console.log("Reason:", `${error}`);
console.log("Endpoint:", `${request.method} ${request.url}`);
console.groupEnd();
});
const sdk = new Paygentic({ httpClient: httpClient });Debugging
You can setup your SDK to emit debug logs for SDK requests and responses.
You can pass a logger that matches console's interface as an SDK option.
[!WARNING] Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.
import { Paygentic } from "@paygentic/sdk";
const sdk = new Paygentic({ debugLogger: console });You can also enable a default debug logger by setting an environment variable PAYGENTIC_DEBUG to true.
Development
Maturity
This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.
Contributions
While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.
