Ray Deck shows how the SaveChange Chrome extension generates curl commands for Xano API endpoints with one click. The extension reads your endpoint's metadata and outputs a ready-to-copy curl with the correct URL, method, body, and auth headers. You can paste it into a terminal, text editor, or Postman, or feed it to AI to generate front-end code.
Xano is great for making APIs, right? These endpoints which you're going to use on your front end or use with other systems or whatever. And there's some, you know, first-party integrations that make that relatively easy to do. And now you also have the ability to, you know, click on create, copy the endpoint URL and bring that into, you know, up here to sort of see exactly what the URL would be that's going to come from one of these particular endpoints. But, you know, when we're importing an API endpoint to another system, it'd be really helpful to have an example, right? Like a curl example, like we see in other API documentation. And now with the SaveChange extension, you can do that. And this is actually a free feature. So if you have the SaveChange extension, which you can just sort of get from Google Chrome Store, and there's gonna be a link to that in the description, you can immediately, you will see some additional buttons show up. One of which is going to be this Get Curl Example button. And this Get Curl Example button will, if you click on it, you know, give you a demo of what this stuff will all look like. And you can copy that and then you can paste that into the system of your, of your choosing here. So if I were to, you know, go bring over a you know, a text editor here, I can sort of paste it in and it'll just work. If I were to bring up my terminal, I can also paste it into here, you know, paste it, and then I have just a curl command that you can run. You can import into Postman or whatever your preferred system is, and it will just work. Now, you will also notice that like as you have And some of these will include a combination of like regular items as well as, you know, like file items. And it's all based on standard curl syntax. So the @myfile name is going to refer to the, you know, filename that you're passing to curl. It is, you know, if it is something that has a form, a file upload to it, then it will also, and if we click back over here, make sure it is in multipart/form-data. Whereas if I were to, you know, publish this for a second and get rid of that particular element from the published version, you see now it shows as being application/json. So it prefers application/json for data structures that are, you know, clear that way. And if it is not, then it will, you know, facilitate the other. And if it is an authenticated endpoint, it shows the authorization header, you know. And Xano is complicated. There's lots of stuff that you can do to change these things. So, you know, You know, this curl command is based on the hints that it's seeing from Xano itself. If you have additional requirements or additional ways that your system works, it may well be that it's not quite enough. And, but I think for the majority of cases, this is going to be pretty helpful. So now, now you have the ability to go grab those curl examples and you can grab them from your individual endpoints as well as just from your groups like we have here. Like you have your authentication/login, great. You get to just sort of, you know, plug that in, copy and paste that, put the curl command where you need it. It to. Uh, I also find these curl commands to be really useful for giving to AI, uh, to give it hints as to what kind of JavaScript it should create, like the front end, to build out Cody stuff for you. Uh, but you can experiment with all that at your convenience, and please let me know in the comments about any, uh, you know, questions you have or suggestions for improvement, because we're all about trying to make working with Xano, uh, go as easily as it can. Uh, I'll talk to you again soon. Bye!
