@vercel/copper
Advanced tools
Developer-friendly & type-safe Typescript SDK specifically catered to leverage *@vercel/copper* API.
Developer-friendly & type-safe Typescript SDK specifically catered to leverage @vercel/copper API.
[!IMPORTANT] This SDK is not yet ready for production use. To complete setup please follow the steps outlined in your workspace. Delete this section before > publishing to a package manager.
Copper: Vercel's internal Billing & Usage Platform
The SDK can be installed with either npm, pnpm, bun or yarn package managers.
npm add @vercel/copper
pnpm add @vercel/copper
bun add @vercel/copper
yarn add @vercel/copper zod
# Note that Yarn does not install peer dependencies automatically. You will need
# to install zod as shown above.
For supported JavaScript runtimes, please consult RUNTIMES.md.
import { Copper } from "@vercel/copper";
const copper = new Copper({
token: process.env["COPPER_TOKEN"] ?? "",
});
async function run() {
const result = await copper.auditLog.list({
requestBody: {},
});
// Handle the result
console.log(result);
}
run();
This SDK supports the following security scheme globally:
| Name | Type | Scheme | Environment Variable |
|---|---|---|---|
token | http | HTTP Bearer | COPPER_TOKEN |
To authenticate with the API the token parameter must be set when initializing the SDK client instance. For example:
import { Copper } from "@vercel/copper";
const copper = new Copper({
token: process.env["COPPER_TOKEN"] ?? "",
});
async function run() {
const result = await copper.auditLog.list({
requestBody: {},
});
// Handle the result
console.log(result);
}
run();
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.
auditLogList - ListcreditBlockGet - GetcreditBlockList - ListcreditLedgerCredit - CreditcreditLedgerDebit - DebitcreditLedgerGet - GetcreditLedgerList - ListcreditLedgerRefund - RefundcreditTopupCreate - CreatecreditTopupDelete - DeletecreditTopupGet - GetcreditTopupList - ListcreditTopupUpdate - UpdatecreditTransactionGet - GetcreditTransactionList - ListplanChangeCommit - CommitplanChangeCreate - CreateplanChangeDelete - DeleteplanChangeGet - GetplanChangeList - ListplanChangeUpdate - UpdateplanClassCreate - CreateplanClassGet - GetplanClassList - ListplanClassUpdate - UpdateplanCreate - CreateplanGet - GetplanList - ListplanUpdate - UpdateproductCreate - CreateproductGet - GetproductList - ListproductUpdate - UpdatepurchaseIntentComplete - CompletepurchaseIntentConfirm - ConfirmpurchaseIntentCreateStripeElementsV1 - CreateStripeElementsV1purchaseIntentCreateStripeHostedV1 - CreateStripeHostedV1purchaseIntentCreateStripeInvoiceDeferredV1 - CreateStripeInvoiceDeferredV1purchaseIntentCreateStripeInvoiceImmediateV1 - CreateStripeInvoiceImmediateV1purchaseIntentGet - GetpurchaseIntentList - ListusageMetricCreate - CreateusageMetricGet - GetusageMetricList - ListusageMetricUpdate - UpdateSome 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 { Copper } from "@vercel/copper";
const copper = new Copper({
token: process.env["COPPER_TOKEN"] ?? "",
});
async function run() {
const result = await copper.auditLog.list({
requestBody: {},
}, {
retries: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
});
// Handle the result
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 { Copper } from "@vercel/copper";
const copper = new Copper({
retryConfig: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
token: process.env["COPPER_TOKEN"] ?? "",
});
async function run() {
const result = await copper.auditLog.list({
requestBody: {},
});
// Handle the result
console.log(result);
}
run();
Some methods specify known errors which can be thrown. All the known errors are enumerated in the models/errors/errors.ts module. The known errors for a method are documented under the Errors tables in SDK docs. For example, the list method may throw the following errors:
| Error Type | Status Code | Content Type |
|---|---|---|
| errors.CopperError | 400, 401, 403, 422 | application/json |
| errors.CopperError | 500 | application/json |
| errors.SDKError | 4XX, 5XX | */* |
If the method throws an error and it is not captured by the known errors, it will default to throwing a SDKError.
import { Copper } from "@vercel/copper";
import { CopperError, SDKValidationError } from "@vercel/copper/models/errors";
const copper = new Copper({
token: process.env["COPPER_TOKEN"] ?? "",
});
async function run() {
let result;
try {
result = await copper.auditLog.list({
requestBody: {},
});
// Handle the result
console.log(result);
} catch (err) {
switch (true) {
// The server response does not match the expected SDK schema
case (err instanceof SDKValidationError): {
// Pretty-print will provide a human-readable multi-line error message
console.error(err.pretty());
// Raw value may also be inspected
console.error(err.rawValue);
return;
}
case (err instanceof CopperError): {
// Handle err.data$: CopperErrorData
console.error(err);
return;
}
case (err instanceof CopperError): {
// Handle err.data$: CopperErrorData
console.error(err);
return;
}
default: {
// Other errors such as network errors, see HTTPClientErrors for more details
throw err;
}
}
}
}
run();
Validation errors can also occur when either method arguments or data returned from the server do not match the expected format. The SDKValidationError that is thrown as a result will capture the raw value that failed validation in an attribute called rawValue. Additionally, a pretty() method is available on this error that can be used to log a nicely formatted multi-line string since validation errors can list many issues and the plain error string may be difficult read when debugging.
In some rare cases, the SDK can fail to get a response from the server or even make the request due to unexpected circumstances such as network conditions. These types of errors are captured in the models/errors/httpclienterrors.ts module:
| HTTP Client Error | Description |
|---|---|
| RequestAbortedError | HTTP request was aborted by the client |
| RequestTimeoutError | HTTP request timed out due to an AbortSignal signal |
| ConnectionError | HTTP client was unable to make a request to a server |
| InvalidRequestError | Any input used to create a request is invalid |
| UnexpectedClientError | Unrecognised or unexpected error |
You can override the default server globally by passing a server index to the serverIdx: number optional parameter when initializing the SDK client instance. The selected server will then be used as the default on the operations that use it. This table lists the indexes associated with the available servers:
| # | Server | Description |
|---|---|---|
| 0 | https://api.vercel.com/copper | Production |
| 1 | https://api.vercel.com/copper-test | Production (Test) |
| 2 | https://api.vercel-infra-dev.com/copper-test | Staging |
import { Copper } from "@vercel/copper";
const copper = new Copper({
serverIdx: 2,
token: process.env["COPPER_TOKEN"] ?? "",
});
async function run() {
const result = await copper.auditLog.list({
requestBody: {},
});
// Handle the result
console.log(result);
}
run();
The default server can also be overridden globally by passing a URL to the serverURL: string optional parameter when initializing the SDK client instance. For example:
import { Copper } from "@vercel/copper";
const copper = new Copper({
serverURL: "https://api.vercel-infra-dev.com/copper-test",
token: process.env["COPPER_TOKEN"] ?? "",
});
async function run() {
const result = await copper.auditLog.list({
requestBody: {},
});
// Handle the result
console.log(result);
}
run();
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 use the "beforeRequest" hook to to add a
custom header and a timeout to requests and how to use the "requestError" hook
to log errors:
import { Copper } from "@vercel/copper";
import { HTTPClient } from "@vercel/copper/lib/http";
const httpClient = new HTTPClient({
// fetcher takes a function that has the same signature as native `fetch`.
fetcher: (request) => {
return fetch(request);
}
});
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 Copper({ httpClient });
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 { Copper } from "@vercel/copper";
const sdk = new Copper({ debugLogger: console });
You can also enable a default debug logger by setting an environment variable COPPER_DEBUG to true.
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.
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.
FAQs
Developer-friendly & type-safe Typescript SDK specifically catered to leverage *@vercel/copper* API.
The npm package @vercel/copper receives a total of 0 weekly downloads. As such, @vercel/copper popularity was classified as not popular.
We found that @vercel/copper demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 9 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
AGENTS.md is a fast-growing open format giving AI coding agents a shared, predictable way to understand project setup, style, and workflows.
Security News
/Research
Malicious npm package impersonates Nodemailer and drains wallets by hijacking crypto transactions across multiple blockchains.
Security News
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.