📎Product metadata

Please ensure that you copy and paste the metadata tags exactly as shown in our guides to avoid any errors.

The amount metadata/parameter in the Data Center and Accounts tabs determines the quantity to be delivered. This is especially useful when using automatic delivery mode, as it ensures that the system delivers exactly the specified amount.

For example, if you are selling subnets that come in blocks of 254 ISPs, you can stack these blocks together. The automatic mode will then deliver the correct number of subnets to the appropriate user based on the quantity defined.

Residential Product

✅Onboarding a residential product

API	First metadata field	Second metadata field	Quantity metadata
Oxylabs	torchlabs_product	torchlabs_elite	data_gb
Smart Proxies	torchlabs_product	torchlabs_smart	data_gb
Bright Data	torchlabs_product	torchlabs_brightdata	data_gb
IPRoyal	torchlabs_product	torchlabs_iproyal	data_gb
Plan X (Private Hybrid Pool)	torchlabs_product	torchlabs_planx	data_gb
Packet Stream	torchlabs_product	torchlabs_basic	data_gb
Geonode	torchlabs_product	torchlabs_geonode	data_gb
Netnut	torchlabs_product	torchlabs_netnut	data_gb
More soon..

Example:

This is an example of a PacketStream product.

The first field input, torchlabs_product, is a tag that helps us identify products created for the proxy dashboard, as opposed to other products on your Stripe account.

The second field, torchlabs_basic, is used to identify the PacketStream API.

The next example refers to the quantity in the price section. In this case, the customer will see a product on the dashboard offering 15 GB of the Killer Basic plan for $140.

We use the data_gb metadata tag to identify the amount of data that needs to be delivered. If this tag is set incorrectly, no data will be delivered to the customer.

In the field next to data_gb, you must enter the actual quantity in gigabytes. For this example, the value should be 15 only include the number, not the letters "GB."

Data center Product

✅Adding data center products

The following metadata is used for unique identification, allowing you to allocate products under different metadata titles.

The names that include "daily," "weekly," or "monthly" are only for identification purposes. You don’t need to follow their literal meaning when assigning products. Any of these metadata names can be used for any product.

Product	First metadata field	Second metadata field	Quantity metada
Product 1	torchlabs_product	torchlabs_datacenter_daily	amount
Product 2	torchlabs_product	torchlabs_datacenter_weekly	amount
Product 3	torchlabs_product	torchlabs_datacenter_monthly	amount
Product 4	torchlabs_product	torchlabs_datacenter_extra1	amount
Product 5	torchlabs_product	torchlabs_datacenter_extra2	amount
Product 6	torchlabs_product	torchlabs_datacenter_extra3	amount
Product 7	torchlabs_product	torchlabs_datacenter_extra4	amount
Product 8	torchlabs_product	torchlabs_datacenter_extra5	amount
Product 9	torchlabs_product	torchlabs_datacenter_extra6	amount
Product 10	torchlabs_product	torchlabs_datacenter_extra7	amount
Product 11	torchlabs_product	torchlabs_datacenter_extra8	amount
Product 12	torchlabs_product	torchlabs_datacenter_extra9	amount
Product 13	torchlabs_product	torchlabs_datacenter_extra10	amount
Product 14	torchlabs_product	torchlabs_datacenter_extra11	amount
Product 15	torchlabs_product	torchlabs_datacenter_extra12	amount
Product 16	torchlabs_product	torchlabs_datacenter_extra13	amount
Product 17	torchlabs_product	torchlabs_datacenter_extra14	amount
Product 18	torchlabs_product	torchlabs_datacenter_extra15	amount
Product 19	torchlabs_product	torchlabs_datacenter_extra16	amount
Product 20	torchlabs_product	torchlabs_datacenter_extra17	amount
Product 21	torchlabs_product	torchlabs_datacenter_extra18	amount
Product 22	torchlabs_product	torchlabs_datacenter_extra19	amount
Product 23	torchlabs_product	torchlabs_datacenter_extra20	amount
Product 24	torchlabs_product	torchlabs_datacenter_extra21	amount
Product 25	torchlabs_product	torchlabs_datacenter_extra22	amount
Product 26	torchlabs_product	torchlabs_datacenter_extra23	amount
Product 27	torchlabs_product	torchlabs_datacenter_extra24	amount
Product 28	torchlabs_product	torchlabs_datacenter_extra25	amount
Product 29	torchlabs_product	torchlabs_datacenter_extra26	amount
Product 30	torchlabs_product	torchlabs_datacenter_extra27	amount
Product 31	torchlabs_product	torchlabs_datacenter_extra28	amount
Product 32	torchlabs_product	torchlabs_datacenter_extra29	amount
Product 33	torchlabs_product	torchlabs_datacenter_extra30	amount

Example

This is an example of a Datacenter product.

The first field, torchlabs_product, is a tag that helps us identify products created for the proxy dashboard versus other products on your Stripe account.

The second field, torchlabs_weekly, is used to identify a unique product.

There is often some confusion about the terms daily, weekly, and monthly in the metadata. These labels actually don’t have any literal meaning. They are only used to differentiate between the various Datacenter products and can be used interchangeably.

For example, if you are selling YeezySupply daily proxies, you can assign any of the three metadata tags without affecting the product.

The next example refers to the quantity in the price section. In this case, the customer will see a product on the dashboard offering 100 Killer ISPs for $300.

We use the amount metadata tag to identify the quantity that needs to be delivered. If this tag is incorrect, no data will be delivered to the customer.

In the field next to amount, enter the actual quantity in units. For this example, the value should be 100. Only the number, without the letters "ISP."

Account Product

With the Accounts Product, you can make up to 9 unique products (if you need more let us know!) and unlike datacenter, the metadata is all the same for all the products... We use some magic behind the scene to make it all work!

✅Adding account products

Product	First metadata field	Second metadata field	Quantity metadata
Product 1 - 9	torchlabs_product	torchlabs_accounts	amount

You can repeat the above metadata for up to 9 products.

Example:

This is an example of an Account product.

The first field, torchlabs_product, is a tag that helps us identify products created for the proxy dashboard versus other products on your Stripe account.

The second field, torchlabs_accounts, is used to identify a specific accounts product.

The next example refers to the quantity in the price section. In this example, we are using the Accounts tab to sell ISP subnets, but you can sell any type of product, such as Gmail or FLX accounts.

In our example, the customer will see a product on the dashboard for 254 Killer ISPs for $400. We use the amount metadata tag to identify the quantity that needs to be delivered. If this tag is incorrect, no data will be delivered.

In the field next to amount, enter the actual quantity in units. For this example, the value should be 254. Only the number, without the letters "ISP."

Again, this method works for any type of product, not just ISPs.