Key Features:
1. STL to G-Code Conversion: Seamlessly convert your 3D models in STL format into G-Code, the language that 3D printers understand. Our API optimizes the model for the printing process, ensuring precision and accuracy.
2. Custom Slicing Parameters: Tailor the slicing process to your specific needs. You can customize a range of slicing parameters, including layer thickness, print speed, infill density, and support structures. This empowers you to fine-tune the output according to the requirements of your 3D printing project.
3. FTP Upload for Easy Access: Once the slicing is complete, your G-Code files are automatically uploaded to an FTP web server, providing a convenient and secure location for downloading. This streamlined process saves you time and ensures your G-Code files are readily accessible.
Our STL Slicing API is a powerful and versatile tool for transforming 3D models in STL format into the essential G-Code files used for 3D printing. With a focus on simplicity and customization, our API allows you to effortlessly convert your STL files into G-Code with just a few simple requests.
STL to G-Code Slicer - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] File Binary |
{"gcode_http_url":"https://www.3dslicegenius.com/gcode_repo/your_file.gcode"}
curl --location 'https://zylalabs.com/api/3022/stl+to+g-code+slicer+api/3193/stl+to+g-code+slicer' \
--header 'Content-Type: application/json' \
--form 'image=@"FILE_PATH"'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
This API supports over 800+ slicing parameters, A list of the slicing parameters is here: https://github.com/Ultimaker/Cura/blob/main/resources/definitions/fdmprinter.def.json For sending slicing parameters please append the required parameters with a prefix '-s' as showing the example below: `-s roofing_monotonic=true -s roofing_layer_count=0 -s infill_material_flow="100"` Please remember, not to remove the default parameters. The default parameters are the below: '-s roofing_monotonic=true -s roofing_layer_count=0' Expect an API error response if the given parameters are mistyped, or with the wrong type of values (for example: str instead of int).
This is due to the limitation of Zyla API Hub. Zyla does not pass the original filename with the API request body.
1. STL file in the API request body as a binary object with an extension of *.stl 2. The slicing parameters are as a param in the URL
The API returns a JSON object containing the URL of the generated G-Code file. The key field in the response is "gcode_http_url," which provides a direct link to download the G-Code.
Users can customize the G-Code output by specifying various slicing parameters in the API request. Parameters include layer thickness, print speed, infill density, and support structures, allowing for tailored slicing based on project needs.
The returned data is in JSON format. The primary structure includes a single key-value pair, where the key is "gcode_http_url" and the value is the URL linking to the generated G-Code file.
Typical use cases include converting STL files for 3D printing, customizing print settings for specific materials, and automating the slicing process in production workflows, enhancing efficiency in 3D printing projects.
Data accuracy is maintained through the use of established slicing algorithms and default parameters. Users can also customize parameters to ensure the output meets specific printing requirements, enhancing precision.
If slicing parameters are incorrect or mistyped, the API will return an error response. Users should verify parameter types and values to ensure they conform to the expected formats to avoid errors.
No, the API processes one STL file per request, generating a single G-Code file. For multiple files, users must make separate API requests for each STL file.
Once the slicing is complete, the G-Code files are automatically uploaded to an FTP server. Users can download the files using the URL provided in the API response under "gcode_http_url."
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
81%
Response Time:
4,117ms
Service Level:
99%
Response Time:
2,360ms
Service Level:
100%
Response Time:
1,429ms
Service Level:
100%
Response Time:
182ms
Service Level:
85%
Response Time:
2,547ms
Service Level:
100%
Response Time:
157ms
Service Level:
100%
Response Time:
1,915ms
Service Level:
100%
Response Time:
114ms
Service Level:
100%
Response Time:
588ms
Service Level:
100%
Response Time:
552ms
Service Level:
100%
Response Time:
321ms
Service Level:
100%
Response Time:
547ms
Service Level:
100%
Response Time:
907ms
Service Level:
100%
Response Time:
239ms
Service Level:
100%
Response Time:
219ms
Service Level:
100%
Response Time:
3,552ms
Service Level:
100%
Response Time:
171ms
Service Level:
100%
Response Time:
168ms
Service Level:
100%
Response Time:
139ms
Service Level:
100%
Response Time:
3,844ms