Key Concepts
Get a quick primer on the key concepts and terminology that we use throughout the product and documentation to get you started quickly.
Last updated
Was this helpful?
Get a quick primer on the key concepts and terminology that we use throughout the product and documentation to get you started quickly.
Last updated
Was this helpful?
Your Xano instance is the heart of everything you do in Xano. An instance is a dedicated server that we manage for you and it contains all of your Xano data, including APIs, databases, user data, and more.
On all of our paid plans, each instance has its own dedicated resources, is always available, and completely isolated from other Xano users. This means that even if, in the rare occurrence that one user experiences an issue with their own Xano backend, it won't impact anybody else.
On our free plan, you are on a shared instance with other Xano users.
In your Xano instance, you can have multiple workspaces. Think of a workspace as a separate container for each project you're building in Xano. Your workspaces are completely isolated from each other, but all share the same compute resources provided by your instance.
Think of the backend as the brains of a website or app. It's all the behind-the-scenes action that users don't see. When you're browsing an online store, the backend is figuring out what products to show you, keeping track of your shopping cart, and making sure your payment goes through. It's like the engine room of a ship - not glamorous, but absolutely crucial.
The frontend is everything you see and interact with on a website or app. It's the pretty face that greets you when you land on a page. This includes the layout, colors, buttons, and forms you fill out. A good frontend makes using a website feel smooth and intuitive, like a well-designed cockpit in an airplane. It's all about creating a great user experience.
A database is essentially a digital warehouse for information. It's where websites and apps store all their data in an organized way. Need to look up a customer's order history? That's stored in a database. Want to see all products under $50? The database has that info too. It's like a super-efficient librarian who can find any piece of information in milliseconds.
Variables are like containers or labels that store information you want to use later in a workflow. Think of them as named boxes where you can keep different types of items, such as numbers, words, or lists. You give each box a name so you can easily find and use the information it holds whenever you need it in your project. This makes it simple to update or change the data without needing to rewrite everything.
Variables are temporary and exist only while a workflow is running, used for storing information you need to access quickly, whereas values in a database are like records in a filing cabinet, stored permanently until you decide to update or delete them, accessible across various workflows and sessions. This makes databases ideal for managing large sets of data over time, and variables more appropriate for temporary data handling.
JSON is a handy way of formatting data that's easy for both humans and computers to understand. JSON organizes information into simple key-value pairs, kind of like a really well-structured grocery list. It's lightweight and flexible, which is why developers love using it to pass data between servers and web applications.
For an example of how JSON can supercharge your data structure, take this example of a hand-written grocery list compared to a JSON equivalent.
JSON follows a structure of key: value pairs. The key typically defines what the value represents, and the value is the actual value itself.
While it may seem similar, JSON is not code. It is just a standard way to structure data. For a real-world comparison, maybe you have a favorite news site or blog that you visit daily. You are used to the format they provide so the information is easily digestible. Now, imagine if every day, they decided to follow a different, unorganized structure instead. This is why data standardization is important, and JSON is a very effective way of achieving this.
An object represents the whole of a thing, such as a person, place, vehicle, form submission -- the possibilities are endless and fully dependent on what you are building. A JSON object can have multiple keys and values inside.
Here is an example of a JSON object that represents user data.
As you can see, we have our keys, such as name, age, and city, as well as our values, which are the actual data that belongs to this user.
JSON can also represent lists of items, like the example below. It looks almost exactly the same, but now we have multiple people inside of an array, or list, denoted by square brackets.
Values don't just have to be single items, such as a person's name or email. You can also supply other objects or arrays for your values. In the below example, we've added an interests key and supplied an array of text strings for the value.
You may have noticed a few mentions of things like integers or strings when learning about JSON. It is important to know what types of data are valid representations inside of a JSON object. One of the most important things to remember when working with JSON is that quotation marks are incredibly important and can be the difference between something working or falling apart.
🔤 Strings are surrounded by "quotation marks" and are just plain text.
🔢 Integers are numbers that are not decimals. Notice how we do not have quotation marks around 1994 in the example below. If we used "1994" instead, this would become a string.
🔢 Decimals are numbers that contain a decimal point.
✅ Booleans are true or false values.
⛔ Null is a special data type that represents nothing in situations where you need to specify that nothing is provided.
📑 Arrays are lists of things. These could be any other valid JSON data type. You could even have an array of arrays if you wanted.
📄 Objects are collections of key-value pairs enclosed in curly braces. Keys are always strings, but values can be any valid JSON data type.
APIs allow different applications to communicate and share data with each other. When you use Google Maps inside another app, that's an API at work. When you click a Buy Now button on Amazon, APIs are firing at all cylinders behind the scenes.
APIs don't have to only be based on user action, either. For example, most websites implement some sort of tracking to ensure that the user experience is as smooth as possible. When you visit these websites, there are API calls being made as you navigate through their frontend.
APIs set the rules for how different pieces of software can talk to each other, making it possible for developers to integrate various services without starting from scratch.
An API has a few main components.
Query parameters and the request body are kind of the same thing, but sent in an API request in different ways.
Query parameters live as part of the request URL. If the API URL is https://myapi.com/getThings and expects you to send a thingId with your request, you would append it to the URL with ?thingId=99, so your full request URL would be https://myapi.com/getThings?thingId=99. You would typically use query parameters for GET and DELETE endpoints.
Request Body is like a set of query parameters, but sent as a JSON object. It's more flexible when sending complex data types, such as lists, nested objects, or files.
In the Xano visual builder, these are known as inputs. You can add inputs manually, or add a Database Link input to automatically populate and sync all fields from a database table.
The response is whatever the API sends back once it has completed the logic it is meant to perform. An API doesn't necessarily need to deliver a response, but it is typical.
Think of your frontend sending an API request when a user logs in. That API request would probably return information about the user logging in, such as their name, location, or other relevant user data.
A response has a few different pieces, similar to what's included in the request, including response headers and a response body.