Jumbula2

## Sections
• [Introduction](https://app.theneo.io/hassan-jumbula-com/jumbula2/getting-started/introduction.md): Welcome to the Jumbula API Documentation , your gateway to integrating applications and services with the Jumbula platform. The Jumbula API provides a structured, secure, and scalable way to manage core platform resources including families, staff, programs, tickets, coupons, and notifications. Whether you’re building internal tools, automating workflows, or creating external integrations, these APIs give you the flexibility and control you need. This documentation covers all available REST endpoints, grouped into logical categories to help you quickly navigate and implement the features relevant to your use case. Title Description Just getting started? Check out our Quickstart Guide. 🗓️ Need any assistance? Book a meeting
• [About the APIs](https://app.theneo.io/hassan-jumbula-com/jumbula2/getting-started/theneo-api-documentation.md): The Jumbula API enables seamless integration with the Jumbula platform, allowing developers to manage families, programs, staff members, coupons, notifications, and support tickets through a structured and secure RESTful interface. This documentation provides a complete overview of all available endpoints, including request formats, response structures, and recommended usage practices. Note: All endpoint specifications in this documentation are designed to help developers build reliable and scalable integrations with the Jumbula system. Why Use the Jumbula API? RESTful architecture with predictable JSON structures Secure authenticated requests using OAuth tokens Logical grouping of resources for simple navigation Scalable and reliable integration experience Ideal for building apps, dashboards, automations, and custom workflows What You Can Do with the Jumbula API ✔ Authentication & Authorization Use secure OAuth token generation to authenticate every request. ✔ Family Management Create and manage families, participants, parents, emergency contacts, and authorized pickups with a comprehensive set of endpoints designed to handle real-world workflows. ✔ Program Management Create, update, and control program details, staff assignments, and capacity information. ✔ Staff Management Manage staff records, account activation states, invitations, restrictions, and operational status. ✔ Coupon Management Create and update coupon codes to support promotions or discount workflows. ✔ Ticketing System Submit, retrieve, and respond to support tickets, download attachments, and view full ticket threads. ✔ Web Notifications Subscribe users, manage their notification endpoints, resend notifications, and fetch preview/sample data. Why This API Exists The Jumbula API is built to help organizations: Automate repetitive administrative workflows Sync Jumbula data with internal systems Extend Jumbula functionality without relying on manual operations What’s Inside This Documentation Endpoint descriptions for every API category Required parameters and request body schemas Response formats and status codes Authentication rules Real-world examples and usage notes
• [Authentication & Authorization](https://app.theneo.io/hassan-jumbula-com/jumbula2/getting-started/customizing.md): Generate an OAuth access token to authenticate requests across all Jumbula API endpoints. This endpoint supports multiple authentication flows including username/password, refresh token, and external identity providers. Purpose This endpoint issues an access token ( access_token ) and a refresh token ( refresh_token ) that must be used for authorized requests throughout the Jumbula API. All tokens follow standard OAuth security practices and include expiration rules.
• [Basics of APIs](https://app.theneo.io/hassan-jumbula-com/jumbula2/api-reference-guide/basics-of-apis.md): Generate an OAuth access token to authenticate requests across all Jumbula API endpoints. This endpoint supports multiple authentication flows including username/password, refresh token, and external identity providers. HTTP Methods HTTP methods, or verbs, denote actions performed on resources. Theneo APIs support various HTTP methods: GET: Retrieve a representation of a specific resource. Example: Retrieving transaction details. POST: Submit data to create a new resource or trigger a state change. Example: Creating a new customer profile. PUT: Replace all representations of a target resource with the provided payload. Example: Updating a subscription plan. DELETE: Remove a specified resource. Example: Deleting a stored card. PATCH: Apply partial modifications to a resource. Example: Changing the status of an existing order. Parameters Parameters allow customization of API requests and responses. Theneo APIs support four types of parameters: Path Parameters: Integral parts of the endpoint URL, identifying specific resources. Query Parameters: Appended to the endpoint URL to filter or paginate results. Request Body Parameters: Included in the request body, transmitting data to the API server. Response Body Parameters: Represent data returned by the server in response to a request. HTTP Status Codes HTTP status codes communicate the outcome of client requests. Theneo employs HTTP status codes categorized into the following classes: Success (200): The request was successfully processed. Example: Successfully retrieved a resource or completed an action. 400 (Bad Request): The server could not understand the request due to invalid syntax. Example: Missing required parameters in the request. 401 (Unauthorized): Authentication is required and has failed or has not yet been provided. Example: Invalid or missing API key. 402 (Request Failed): The parameters were valid but the request failed. Example: Insufficient funds or expired credit card. 403 (Forbidden): The client does not have access rights to the content. Example: Attempting to access a resource without the necessary permissions. 404 (Not Found): The server can not find the requested resource. Example: Trying to access an endpoint that does not exist.
• [Base URL](https://app.theneo.io/hassan-jumbula-com/jumbula2/api-reference-guide/base-url.md): The Base URL is a crucial element for making API calls, enabling you to clearly specify the root URL(s) for API requests. When making API calls, you combine the base URL with the specific endpoint path to form the complete request URL. It supports multiple environments, including staging and production. Additionally, the base URL synchronizes with the API explorer, allowing you to seamlessly switch between environments like Sandbox and Production while trying out API calls.
• [Authentication API](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy.md): Note: This endpoint allows you to securely obtain an access token that you can use to authenticate your requests across the Jumbula API. To use this endpoint, you will need a clientId and clientSecret , which are unique credentials assigned to your account. If you do not already have these credentials, please contact our support team by submitting a ticket. After verifying your request, our team will provide the required client credentials.
  • [Create a token](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy/create-a-coupon-copy.md): This endpoint is used to authenticate users and generate access tokens for secure communication with the API.
• [Coupon API](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/transaction-api-example.md): Note: All coupon-related APIs allow you to manage discount codes within your Jumbula account. You can create, update, or configure how coupons apply to programs, tuitions, and registrations. Please make sure your coupon dates, usage limits, and program selections are set correctly to avoid unexpected behavior during checkout.
  • [Create a coupon](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/transaction-api-example/create-a-charge.md): Use this endpoint to create a new coupon in your Jumbula account. You can define the coupon code, discount amount, which programs or tuitions it applies to, and when it becomes active. This API makes it easy to automate promotions, seasonal discounts, and special offers for families during registration.
  • [Update a coupon](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/transaction-api-example/update-a-charge.md): This endpoint allows you to update an existing coupon by modifying its details such as code, discount amount, applicable programs, usage limits, and active dates. Use this endpoint when you need to adjust a coupon’s configuration without creating a new one.
• [Family API](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1.md): Note: These APIs provide a complete set of endpoints for managing families and their related data within the system. Using these endpoints, you can create, retrieve, update, and delete family records, including parents, participants (students), authorized pickups, emergency contacts, insurance details, and contact information. The APIs also support searching, filtering, and assigning families to businesses (such as schools), making it easy to manage family profiles, enroll participants, and keep information up to date across different seasons and programs. All endpoints are designed to be simple, consistent, and secure, ensuring smooth integration and an easy developer experience.
  • [Create a family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/create-a-coupon-copy.md): This endpoint allows you to create a new family profile in the Jumbula platform. A family record includes basic account information, contact details, insurance details, and can later be extended with parents, participants, authorized pickups, and emergency contacts. This API is typically used when integrating external systems that need to programmatically sync or provision families into Jumbula.
  • [Get a family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/get-a-family.md): Retrieves full information about a family with all related data, including parents, participant, pickups, emergency contacts, insurance, and contact information.
  • [Update a family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/update-a-coupon-copy.md): This endpoint allows you to update an existing coupon by modifying its details such as code, discount amount, applicable programs, usage limits, and active dates. Use this endpoint when you need to adjust a coupon’s configuration without creating a new one.
  • [Get all family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/update-a-family-copy-2.md): This endpoint returns a complete list of families with all related data, including parents, participant, pickups, emergency contacts, insurance, and contact information. Use query parameters to filter or paginate results.
  • [Delete a family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/delete-a-family.md): This request is used to completely remove a Family from the system. After deletion, all information about that Family—including parents, participants, contact information, and related records—will no longer be available. ⚠️ Important: Deleting a Family cannot be undone. Before submitting a request, make sure that this Family no longer needs access or registration in the system.
  • [Get all family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-1.md): Retrieves a paginated list of families with optional filtering based on family, participant, business, and demographic information. This endpoint is mainly used for searching, filtering, and reporting across families and their participants .
  • [Assign family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/get-all-family-copy.md): This endpoint assigns an existing Family to a specific Business. By providing a businessId , the system links the targeted Family (specified by id in the path) to that Business. After a successful assignment, the full updated Family object is returned.
  • [Add participant to a family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/get-all-family-copy-1.md): This endpoint adds a new participant (child/student) to an existing Family. You must send the participant’s full profile, including personal info, medical info, school info, and contact details. If the request is valid, the participant will be created and linked to the Family.
  • [Update a family participant](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/get-all-family-copy-2.md): This endpoint updates the details of an existing participant (child/student) within a specific Family. You can modify personal information, medical details, school details, and contact fields.
  • [Remove a participant from a family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-2.md): This endpoint permanently removes a participant (child/student) from a specific Family. Use this when a participant no longer belongs to the Family or was added by mistake.
  • [Get participant details](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/get-participant-details.md): Retrieves full information about a single participant (child/student) belonging to a specific Family. Use this endpoint to display participant profiles, edit screens, or verify data.
  • [Get family participants](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/get-participant-details-copy-1.md): Retrieves a list of all participants (children/students) that belong to a specific family. You can use Limit and Offset to paginate the results if the family has many participants.
  • [Get all participants in a family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/get-participant-details-copy.md): Retrieves full information about a single participant (child/student) belonging to a specific Family. Use this endpoint to display participant profiles, edit screens, or verify data.
  • [Search for participants](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy.md): This endpoint allows you to search for participants across all families , using a wide range of filters such as name, email, externalId, family details, business type, phone, and more. It is commonly used when you need to look up participants globally , not limited to a single family.
  • [Update participant externalId](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-1-1.md): This endpoint is used to update the externalId of one or more participants within a specific season. It is commonly used when syncing data with external systems (e.g., school SIS, CRM, etc.). The API receives a list of participants and returns the updated participant profiles.
  • [Add parent to a family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-2-1.md): This endpoint allows you to add a new parent/guardian to an existing family . You provide parent details (contact info, relationship, address, etc.), and the API returns the newly created parent record with its unique id . Use this endpoint whenever you need to register an additional parent, guardian, or family contact.
  • [Update a family parent](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-3.md): This endpoint updates an existing parent/guardian record within a family. You must pass the family ID and the specific parent ID in the URL. All parent fields can be updated, including contact info, relationship details, gender, and home address.
  • [Remove a parent from a family](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-4.md): This endpoint remove an existing parent/guardian record within a family. You must pass the family ID and the specific parent ID in the URL.
  • [Get parent details](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/remove-a-parent-from-a-family-copy.md): Retrieves detailed information for a specific parent or guardian associated with a given family. This endpoint is useful for viewing parent profile details, including contact information, relationship to the participant, and address data.
  • [Get family parents](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-5.md): Retrieves a list of all participants (children/students) that belong to a specific family. You can use Limit and Offset to paginate the results if the family has many participants.
  • [Search parents](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/get-family-parents-copy.md): This endpoint retrieves a list of parents/guardians based on filters such as name, email, externalId, phone, parentId, familyId, and businessId. It is a search/filter API , not a creator endpoint.
  • [Create authorized pickup](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/get-family-parents-copy-1.md): This endpoint is used to add a new authorized pickup contact to a specific family. The created record represents a person who is allowed to pick up a participant from the organization.
  • [Update authorized pickup](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/create-authorized-pickup-copy.md): This endpoint updates an existing authorized pickup contact associated with a specific family. Use this when you need to modify details such as name, relationship, phone numbers, or emergency contact status.
  • [Remove authorized pickup](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-6.md): This endpoint deletes an authorized pickup from a specific family. Use this to permanently remove a pickup contact who is no longer allowed to pick up the child. Once deleted, the contact will no longer appear in the family’s authorized pickup list.
  • [Get authorized pickup details](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-7.md): Retrieve a single authorized pickup contact for a specific family.
  • [Get family authorized pickups](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-8.md): Retrieves a list of all authorized pickups (children/students) that belong to a specific family. You can use Limit and Offset to paginate the results if the family has many participants.
  • [Search authorized pickups](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-9.md): This endpoint retrieves a list of authorized pickups based on filters such as name, email, externalId, phone, parentId, familyId, and businessId. It is a search/filter API , not a creator endpoint.
  • [Create emergency contact](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/create-authorized-pickup-copy-1.md): This endpoint is used to add a new emergency contact to a specific family. The created record represents a person who is allowed to pick up a participant from the organization.
  • [Update emergency contact](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-11.md): This endpoint updates an existing emergency contact associated with a specific family. Use this when you need to modify details such as name, relationship, phone numbers, or emergency contact status.
  • [Remove emergency contact](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-12.md): This endpoint deletes an emergency contact from a specific family. Use this to permanently remove an emergency contact who is no longer allowed to pick up the child. Once deleted, the contact will no longer appear in the family’s emergency contact list.
  • [Get emergency contact details](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-13.md): Retrieve a single emergency contact contact for a specific family.
  • [Get family emergency contacts](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/coupon-api-copy-1/copy-14.md): Retrieves a list of all emergency contacts that belong to a specific family. You can use Limit and Offset to paginate the results if the family has many participants.
• [Dev Tools API Examples](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/hr-management-examples.md): Note: All of the stated endpoints and sections are for demonstration purposes only. Theneo does not manage payments API, get sales data, itemize payments, push orders to POS, and more.
  • [List branches](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/hr-management-examples/list-branches.md): This section allows users to retrieve a list of branches associated with the account. By accessing this API, users can gain insights into the different branches within a repository and their associated information.
  • [Get a branch](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/hr-management-examples/get-a-branch.md): This section allows users to retrieve detailed information about a specific branch within a repository. By accessing this functionality, users can gather essential data related to the branch, such as commit details, author information, and associated URLs, enabling them to better understand the branch's history and contributors.
  • [Rename a branch](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/hr-management-examples/rename-a-branch.md): Renames a branch in a repository. Note: Although the API responds immediately, the branch rename process might take some extra time to complete in the background. You won't be able to push to the old branch name while the rename process is in progress. The permissions required to use this endpoint depends on whether you are renaming the default branch. To rename a non-default branch: Users must have push access. Apps must have the contents:write repository permission. To rename the default branch: Users must have admin or owner permissions. Apps must have the administration:write repository permission.
  • [Get a schedule](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/hr-management-examples/get-a-schedule.md): This section allows users to retrieve schedule information, including details such as hours of the day, days of the week, and months. By accessing this endpoint, users can access essential scheduling data for efficient planning and management within their projects.
  • [Update a schedule](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/hr-management-examples/update-a-schedule.md): This section allows users to update a schedule with specific parameters and details, such as description, timetable settings, and attribution information. By sending a request to this endpoint, users can modify existing schedules to reflect any changes or updates needed within their project or application.
  • [Delete a schedule](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/hr-management-examples/delete-a-schedule.md): The "Delete a schedule" section allows users to remove a scheduled event or task from the system. By utilizing this functionality, users can effectively manage their schedules and ensure accurate records without unnecessary clutter. This feature provides a straightforward way to declutter and streamline the scheduling process.
• [Theneo Real APIs](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/theneo-real-apis.md): Creating intuitive, detailed, and easy-to-navigate API documentation has never been easier. Theneo streamlines every step of the process, ensuring that your documentation is not only comprehensive but also interactive and user-friendly. Here's how you can quickly set up your project in Theneo
  • [Add new project](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/theneo-real-apis/add-new-project.md): This section allows users to add a new project to their account. By providing specific parameters such as project name, key, and logo, users can create a new project with customized settings. The response provides details on the successful creation of the project or any errors encountered during the process.
  • [Get all projects](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/theneo-real-apis/get-all-projects.md): This section allows users to retrieve all projects associated with a specific criteria, such as company ID or publication status. By accessing this endpoint, users can obtain a list of projects along with relevant information such as project name, key, creator, and accessors. This information can be valuable for managing and monitoring projects within the platform.
  • [Get project by id](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/theneo-real-apis/get-project-by-id.md): The "Get project by id" section allows users to retrieve detailed information about a specific project within the system. By providing the project's unique identifier, users can access essential details such as project name, key, company ID, and creation information. This functionality enables users to efficiently access and review project-specific data for their workflow needs.
  • [Delete project](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/theneo-real-apis/delete-project.md): This section allows users to delete a project from the system, removing all associated data and configurations. By utilizing this API functionality, users can efficiently manage their project list and ensure accurate data organization within the platform.
  • [Get accessible users](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/theneo-real-apis/get-accessible-users.md): This section allows users to retrieve a list of accessible users within a specific project. Users can access information such as user IDs, names, contact details, and account status to manage project access permissions effectively.
  • [Share a project](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/theneo-real-apis/share-a-project.md): This section allows users to share a project with other users by specifying their user IDs, email addresses, and roles. Users can choose to make the project public and opt to receive notifications when others interact with the shared project.
  • [Change user access to a project](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/theneo-real-apis/change-user-access-to-a-project.md): This section allows users to modify the access permissions for a specific user within a project. By changing the user's access level or removing them entirely, users can effectively manage project collaboration and security settings. This feature provides flexibility and control over project access rights.
  • [Import API specification](https://app.theneo.io/hassan-jumbula-com/jumbula2/rest-api-reference/theneo-real-apis/import-api-specification.md): The Import API specification section allows users to import project data into the system, enabling seamless migration or integration of project information. With this feature, users can effortlessly transfer project details and associated data to streamline their workflow within the application.
• [Payments / Banking API example](https://app.theneo.io/hassan-jumbula-com/jumbula2/soap-api-referenc/payments-banking-api-example.md): Note: All of the stated endpoints and sections are for demonstration purposes only. Theneo does not manage payments API, get sales data, itemize payments, push orders to POS, and more.
  • [Create bank account](https://app.theneo.io/hassan-jumbula-com/jumbula2/soap-api-referenc/payments-banking-api-example/create-bank-account.md): Creates a new bank account.
  • [Create entity](https://app.theneo.io/hassan-jumbula-com/jumbula2/soap-api-referenc/payments-banking-api-example/create-entity.md): How to create a new Customer or Supplier.
  • [Create invoice](https://app.theneo.io/hassan-jumbula-com/jumbula2/soap-api-referenc/payments-banking-api-example/create-invoice.md): Create a new invoice.
  • [Delete entity](https://app.theneo.io/hassan-jumbula-com/jumbula2/soap-api-referenc/payments-banking-api-example/delete-entity.md): Delete an existing Customer or Supplier.
  • [Get invoice ID by number](https://app.theneo.io/hassan-jumbula-com/jumbula2/soap-api-referenc/payments-banking-api-example/get-invoice-id-by-number.md): Returns the latest invoice ID for an invoice prefix and invoice number pair.
  • [List bank accounts](https://app.theneo.io/hassan-jumbula-com/jumbula2/soap-api-referenc/payments-banking-api-example/list-bank-accounts.md): Lists the existing bank accounts on the account.
• [Query](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/query.md): Note: All of the stated endpoints and sections are for demonstration purposes only. Theneo does not manage payments API, get sales data, itemize payments, push orders to POS, and more. The Query type in GraphQL represents the entry point for retrieving data from the API. It defines the available read-only operations (queries) that clients can execute to fetch data.
  • [continent](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/query/continent.md): The "continent" section allows users to query for information about a specific continent, including its code, name, and a list of countries within that continent. Users can retrieve details such as country codes, names, native names, currencies, languages, and emojis related to the continent and its countries. This section provides comprehensive data on continents and their associated countries for use in various applications.
  • [country](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/query/country.md): The country section allows users to retrieve detailed information about a specific country based on its unique country code. Users can access data such as the country's name, native name, phone code, currency, languages spoken, and even its flag emoji. This section provides comprehensive insights into individual countries for various analysis and reference purposes.
  • [language](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/query/language.md): The "language" section allows users to retrieve information about a specific language based on its code. By making a query with the language code as a parameter, users can access details such as the language's name, native form, and writing direction (rtl). This section helps developers access and display language-specific information within their applications.
• [Objects](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/objects.md): Objects in GraphQL represent complex data structures. They define the fields and their types that can be queried in a GraphQL API. Objects can have nested fields and relationships with other objects.
  • [Continent](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/objects/continent.md): The Continent section of the Blank API allows users to retrieve information related to continents. By utilizing this section, users can access data such as continent names, populations, and geographical features. This functionality enables developers to incorporate continent-specific information into their applications with ease.
  • [Country](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/objects/country.md): The Country section provides users with a comprehensive list of supported countries and their corresponding details. Users can utilize this information to customize their services based on specific countries, such as currency settings, language preferences, and regulatory requirements. This section serves as a valuable resource for developers looking to expand their global reach and cater to diverse international markets effectively.
  • [Language](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/objects/language.md): The Language section of the Blank API allows users to manage and manipulate linguistic data associated with their projects. Users can access language-related functionalities to enhance text processing and analysis within their applications.
• [Scalars](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/scalars.md): Scalars: Scalars in GraphQL represent primitive data types, such as String, Int, Boolean, Float, etc. They are used to define the types of individual fields in the GraphQL schema.
  • [Boolean](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/scalars/boolean.md): Represents a boolean value that can be either true or false.
  • [Float](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/scalars/float.md): A signed double-precision floating-point value.
  • [ID](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/scalars/id.md): A unique identifier, often used to refetch an object or as a key for caching.
  • [Int](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/scalars/int.md): A signed 32-bit integer.
  • [String](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/scalars/int-1.md): A UTF-8 character sequence.
  • [Upload](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/scalars/upload.md): The Upload scalar type represents a file upload.
• [Directives](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/directives.md): Directives in GraphQL provide a way to control the execution behavior of queries and mutations. They allow you to modify the result, change the execution order, skip or include fields conditionally, and apply custom logic to the resolution process.
  • [cacheControl](https://app.theneo.io/hassan-jumbula-com/jumbula2/graphql-api-reference/directives/cachecontrol.md): The cacheControl section allows users to manage caching behavior for improved performance and reduced load times. By adjusting cache settings, users can control how often data is retrieved from the server, optimizing the efficiency of API requests and enhancing overall user experience. This section empowers users to fine-tune caching strategies to meet their specific needs and requirements.