Datapel Systems

## 🚀 Theneo

Theneo is the quickest, simplest way to generate high-quality, interactive API docs. Just import your API collection and we'll take care of the rest.

**⚠️ 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 Orders API provides a one-stop shop for integrating advanced payment functionality. You can itemize payments with custom line items or catalog objects, send orders to real Point of Sale devices to be fulfilled, and more.In addition, the Orders API allows you to look through all of a seller's previous sales and returns itemization data, customer references, and other information from POS or online transactions.

&lt;img src="https://assets.website-files.com/61f7e03934c23c1dcc9c3cd4/6306089ecc13c15fe0a7e006_Main page_2 (with visual studoi code logo) 2.svg" alt="" height="237" width="322">

### Generate API Documentation

- Build interactive API docs
- Tailor you documentation
- Create and launch quickly
- Update easily within seconds
- Built for everyone
    

# Integrations

Import your collections manually or use our integrations to automatically migrate your work from:

- Swagger
- Postman
- Github
    

[  
](https://www.theneo.io/#)

[  
](https://app.theneo.io/signup)

Datapel API Reference

How it Works

OData Standards Support

OData Web Components

OData Best Practices

🚀 Theneo is the quickest, simplest way to generate high-quality, interactive API docs. Just import your API collection and we'll take care of the rest.

⚠️ 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 Orders API provides a one-stop shop for integrating advanced payment functionality. You can itemize payments with custom line items or catalog objects, send orders to real Point of Sale devices to be fulfilled, and more.In addition, the Orders API allows you to look through all of a seller's previous sales and returns itemization data, customer references, and other information from POS or online transactions.

&lt;img src="https://assets.website-files.com/61f7e03934c23c1dcc9c3cd4/6306089ecc13c15fe0a7e006_Main page_2 (with visual studoi code logo) 2.svg" alt="" height="168" width="200">

### Generate API Documentation

- Build interactive API docs
- Tailor you documentation
- Create and launch quickly
- Update easily within seconds
- Built for everyone
    

# Integrations

Import your collections manually or use our integrations to automatically migrate your work from:

- Swagger
- Postman
- Github

Authentication

Token

Creates a new customer for a business.

You must provide at least one of the following values in your request to this endpoint:

 *   `given_name`
 *   `family_name`
 *   `company_name`
 *   `email_address`
 *   `phone_number`

Token Refresh

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.

**⚠️ Note:** The Orders API provides a one-stop shop for integrating advanced payment functionality. You can itemize payments with custom line items or catalog objects, send orders to real Point of Sale devices to be fulfilled, and more.

In addition, the Orders API allows you to look through all of a seller's previous sales and returns itemization data, customer references, and other information from POS or online transactions.

&lt;img src="https://media.geeksforgeeks.org/wp-content/cdn-uploads/20200318193845/Top-7-Payment-Gateway-APIs-That-Every-Developer-Must-Know.png">

As an organization, you need to be careful while choosing a payment gateway option. It should be according to the customer’s experience on your websites through to cash flow to online sales. Make sure that you take care of at least 5 things mentioned below while choosing a payment gateway… 

- **Security** should be the topmost priority. Make sure that it should be integrated with the 3D security and comply with the PCI Data Security Standard (PCI DSS).
- **Payout Time** should be less to credit money in your bank account.
- **Integration need to be easy and simple** or it can develop a custom-coded solution for your platform easily.
- **Multiple currencies** should be handled by the payment gateway for the customers using different currencies across the world.

Endpoint Reference

Creates a new order that can include information about products for purchase and settings to apply to the purchase.

Time Stamp

List Items

Ship Methods

Sources

Tax Codes

Job Codes

Audit Events

Product List

Inventory List

Inventory Events

Address List

Contact List

Location List

Attachments

Create Sale Order

Order List

Create Transfer Order

Transfer Order List

Create Purchase Order

Inward Order List

Create Transaction

Workspace Options

Change Log

Theneo Demo TechCrunch

Datapel API

Production

Sandbox

<p class="slate-p " >Welcome to the API Reference for the Datapel Cloud.WMS Inventory Management System (IMS), a powerful and versatile tool designed to streamline the management of order and inventory data for businesses of all sizes. This documentation serves as your comprehensive guide to understanding and use of our API, providing you with the information and resources needed to integrate our system seamlessly into your applications and processes.</p><h3 class="slate-h3 " ><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">Why an Inventory Management System Matters</strong></span></h3><p class="slate-p " >Efficient order and inventory management is the cornerstone of successful business operations. Whether you are a small wholesaler, a manufacturing powerhouse, or an e-commerce giant, the ability to track, monitor, and control your inventory is essential for reducing costs, improving customer satisfaction, and driving profitability. Our Inventory Management System is designed to simplify this complex task, offering real-time insights, process automation, and scalability.</p><h3 class="slate-h3 " ><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">What Can You Achieve with Our API</strong></span></h3><p class="slate-p " >The Datapel API opens up many possibilities for developers, businesses, and entrepreneurs seeking to optimise their inventory and order management processes. Here are some potential applications and use cases that can and have been developed using our API:</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative"><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">E-commerce Integration</strong></span> Seamlessly sync your e-commerce platform with our WMS to ensure accurate product availability and pricing on your online store. This leads to fewer out-of-stock situations and enhances the overall shopping experience for your customers.
</div></li><li class="slate-li " ><div style="position:relative"><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">Warehouse Automation</strong></span> Implement robotic or IoT solutions to automate inventory movement within your warehouses. Our API provides real-time inventory data, enabling robots or devices to make informed decisions about restocking and retrieval.
</div></li><li class="slate-li " ><div style="position:relative"><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">Multi-Location Management</strong></span> Manage inventory across multiple physical locations, whether they are warehouses, retail stores, or distribution centres. Our API allows you to centralise inventory control and maintain consistency across your network.
</div></li><li class="slate-li " ><div style="position:relative"><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">Customer and Supplier Collaboration</strong></span> Facilitate better communication with your customers and suppliers by sharing real-time inventory data. Suppliers can use this information to optimise production schedules and ensure timely deliveries, reducing the risk of stockouts. Customers can check availability and account status reducing overall customer servicing costs.
</div></li><li class="slate-li " ><div style="position:relative"><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">Inventory Forecasting</strong></span> Utilise historical data and predictive analytics to forecast demand and optimise inventory levels. With our API, you can build custom forecasting algorithms and strategies to minimize overstock and understock situations.
</div></li><li class="slate-li " ><div style="position:relative"><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">Order Fulfillment Automation</strong></span> Create systems that automate order fulfillment processes, ensuring orders are picked, packed, and shipped efficiently, with real-time inventory updates for customers.
</div></li><li class="slate-li " ><div style="position:relative"><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">Inventory Reporting and Analytics</strong></span> Develop custom dashboards and reporting tools to gain valuable insights into your inventory performance. Track key metrics such as turnover rate, holding costs, and sales velocity.
</div></li><li class="slate-li " ><div style="position:relative"><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">Inventory Auditing and Compliance</strong></span> Implement auditing solutions that use the IMS API to verify inventory accuracy and compliance with industry regulations. This is especially crucial in sectors with strict quality control requirements.
</div></li><li class="slate-li " ><div style="position:relative"><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">Inventory Optimization Algorithms</strong></span> Design algorithms that automatically optimise inventory reorder points, safety stock levels, and economic order quantities based on real-time market conditions.
</div></li><li class="slate-li " ><div style="position:relative"><span style="color:var(--tw-prose-bold)"><strong class="slate-bold">Retail Shelf Management</strong></span> Optimise the placement of products on store shelves by utilising our API to ensure high-demand items are always readily available, leading to increased sales.</div></li></ol><p class="slate-p " >The Cloud.WMS API empowers you to take control of your inventory and order management processes and drive operational excellence across your business. Whether you are looking to enhance the efficiency of your supply chain, boost customer satisfaction, or make data-driven decisions, our API is your gateway to achieving these objectives with precision and ease. 
</p><p class="slate-p " >In this API Reference, you will find detailed documentation, code examples, and best practices to help you harness the full potential of our Inventory Management System API.</p><p class="slate-p " >

</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Welcome to the API Reference for the Datapel Cloud.WMS Inventory Management System (IMS), a powerful and versatile tool designed to streamline the management of order and inventory data for businesses of all sizes. This documentation serves as your comprehensive guide to understanding and use of our API, providing you with the information and resources needed to integrate our system seamlessly into your applications and processes.

Why an Inventory Management System Matters

Efficient order and inventory management is the cornerstone of successful business operations. Whether you are a small wholesaler, a manufacturing powerhouse, or an e-commerce giant, the ability to track, monitor, and control your inventory is essential for reducing costs, improving customer satisfaction, and driving profitability. Our Inventory Management System is designed to simplify this complex task, offering real-time insights, process automation, and scalability.

The Datapel API opens up many possibilities for developers, businesses, and entrepreneurs seeking to optimise their inventory and order management processes. Here are some potential applications and use cases that can and have been developed using our API:

The Cloud.WMS API empowers you to take control of your inventory and order management processes and drive operational excellence across your business. Whether you are looking to enhance the efficiency of your supply chain, boost customer satisfaction, or make data-driven decisions, our API is your gateway to achieving these objectives with precision and ease. 


In this API Reference, you will find detailed documentation, code examples, and best practices to help you harness the full potential of our Inventory Management System API.

<h3 class="slate-h3">Retrieving Data</h3><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets"><span style="background-color:rgb(255, 255, 255);color:rgb(90, 90, 90);font-size:14px" class="slate-color"><span style="background-color:rgb(255, 255, 255);color:rgb(90, 90, 90);font-size:14px" class="slate-backgroundColor">Use the HTTP GET method to retrieve data from your workspace via endpoint resources. This includes both lists and individual records. For example, you would use the GET method to retrieve a list of sales orders made in a particular month, or the contact details of a customer. </span></span></p><ul class="slate-ul"><li class="slate-li"><div style="position:relative">Successful responses return with a <a href="https://developer.xero.com/documentation/api/accounting/responsecodes#common-response-codes" target="_blank">HTTP 200</a> status code</div></li><li class="slate-li"><div style="position:relative">By default all successful responses on the Datapel API are returned as JSON.</div></li><li class="slate-li"><div style="position:relative">The API requires a security domain or scope to be provided with TOKEN requests and REFRESH, for public api resources use <span style="color:#6C9EEB" class="slate-color"><strong style="color:#6C9EEB" class="slate-bold">pub</strong></span>.  </div></li><li class="slate-li"><div style="position:relative">Forms and Reports can also be returned in PDF format ensure you apply the correct content type header when required.</div></li><li class="slate-li"><div style="position:relative">Example GET request for a particular product would look like this → <a href="https://api2.datapel.net/api.datapel/v2.0/myaccount/product?34" target="_blank">https://api2.datapel.net/api.datapel/v2.0/pub/product?34</a></div></li></ul><h3 class="slate-h3">JSON responses and date formats</h3><p class="slate-p" placeholder="Type / for widgets">By default JSON formatted responses are returned, be sure to use the http header “application/json” when making a request.</p><p class="slate-p" placeholder="Type / for widgets">Any Date returned in JSON datasets is UTC format represented as <strong class="slate-bold">YYYY-MM-DDTHH:mm:SS</strong>, for example ‘<em style="font-size:11pt" class="slate-italic">2009-04-29T10:12:20’. </em></p><p class="slate-p" placeholder="Type / for widgets">In order to reduce overall data transfer requirements a record level <span style="color:#1155CB" class="slate-color">TIMESTAMP</span> is typically available with format ‘2<em class="slate-italic">021-10-01 16:35:03’ </em>indicating the time this record was <span style="color:#FE9900" class="slate-color">last modified</span>.</p><h3 class="slate-h3">Filtering Data </h3><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">The Datapel API uses the OData standard as the syntax allowing queries of specific data records. By using OData filter queries, you can obtain specific subsets of data, reducing the amount of unnecessary information and enhancing the performance of your workflows.

When using filters, you can use comparison operators like <span style="background-color:transparent;font-size:20px" class="slate-backgroundColor">eq</span> for <span style="background-color:transparent;font-size:20px" class="slate-backgroundColor">equals</span>, <span style="background-color:transparent;font-size:20px" class="slate-backgroundColor">ne</span> for <span style="background-color:transparent;font-size:20px" class="slate-backgroundColor">not equals</span>, and so on. You can also use logical operators such as <span style="background-color:transparent;font-size:20px" class="slate-backgroundColor">and</span>, <span style="background-color:transparent;font-size:20px" class="slate-backgroundColor">or</span>, and <span style="background-color:transparent;font-size:20px" class="slate-backgroundColor">not</span> to combine multiple conditions. Additionally, there are functions to refine string-based searches. For example, <span style="background-color:transparent;font-size:20px" class="slate-backgroundColor">startswith(fieldName,’string’)</span> checks if a field starts with a specified string, <span style="background-color:transparent;font-size:20px" class="slate-backgroundColor">endswith(fieldName,’string’)</span> checks if it ends with one, and <span style="background-color:transparent;font-size:20px" class="slate-backgroundColor">substringof(‘string’,fieldName)</span> verifies if a field contains a particular substring.</p><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">To explore the syntax and example queries review the OData Standards Support section of this reference guide.</p><h3 class="slate-h3">Pagination</h3><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">A single HTTP GET request can return at most 500 records. This is reasonable because most HTTP clients have a timeout limit of 2 - 5 minutes. They do not allow transactions to wait more than that. A request running longer than the limit gets an HTTP timeout error. Therefore, it is often required to tune complex queries and lower the data size for them to complete within the timeout restriction. Long running queries can also degrade server response times to other users and tenants so its best practice to do smaller queries more often than large one off data requests</p><p class="slate-p" placeholder="Type / for widgets">The OData API provides several pagination options for query results.</p><p class="slate-p" placeholder="Type / for widgets">Client-side pagination uses query options on the client side to create an offset that restricts the amount of data returned from the server.</p><p class="slate-p" placeholder="Type / for widgets">A client-side pagination query can be made using the following URI parameters:</p><ul class="slate-ul"><li class="slate-li"><div style="position:relative">The $top parameter indicates the number of records to return in the batch. The default and maximum number is 500 records.</div></li><li class="slate-li"><div style="position:relative">The $skip parameter indicates the number of records in the full data set to skip before fetching data.</div></li></ul><p class="slate-p" placeholder="Type / for widgets">For example, a query with $skip=2000&amp;$top=500 returns the fifth page of data where the page size is 500.</p><p class="slate-p" placeholder="Type / for widgets"><span style="color:#666666" class="slate-color"><strong style="color:#666666" class="slate-bold">Advantages</strong></span></p><ul class="slate-ul"><li class="slate-li"><div style="position:relative">Faster initial page load</div></li><li class="slate-li"><div style="position:relative">It works well with OData compliant list and table web controls to fetch records on demand. DevExtreme UI controls from <a href="https://js.devexpress.com/" target="_self">DevExpress</a> automatically change the $skip value in order to scroll through the data set.</div></li><li class="slate-li"><div style="position:relative">It allows reverse scrolling by decreasing $skip values. This allows UI controls to avoid buffering all data as the user scrolls up and down.</div></li></ul><p class="slate-p" placeholder="Type / for widgets"><span style="color:#666666" class="slate-color"><strong style="color:#666666" class="slate-bold">Considerations when using OData pagination</strong></span></p><ul class="slate-ul"><li class="slate-li"><div style="position:relative">For each page, the query is re-executed and then moves forward through the data set to reach the specified $skip value. Not only is this inefficient but also it can lead to unstable results. The data set could be changing due to simultaneous creating, updating, or deleting of the data. Conversely, most modern databases implement caching and will generally store prior query data so this does not present as a major limitation or issue.</div></li><li class="slate-li"><div style="position:relative">If a record is inserted on a prior page after it has been read, it shifts the data set to the right, resulting the last record from the previous page to be pushed into the current page. This causes the page to be read again because the $skip value of the current page is one record too small, resulting in duplicates in the total data set. You can avoid this issue using $orderBy=TimeStamp to push newly created records to the end of the data set.</div></li><li class="slate-li"><div style="position:relative">If a record is deleted from a prior page after it has been read, it shifts the data set to the left. The first record of the current page is lost because the $skip value of the current page is one record too large. There’s no good workaround when dealing with concurrent hard deletes from the data set. Note these potential data loss issues make &quot;last modified since&quot; queries especially unreliable. If a record is lost in a query, it can only be picked up by a later attempt after it&apos;s modified.</div></li></ul><p class="slate-p" placeholder="Type / for widgets">Most queries will return a total record count which allows your request to select a exact page number, and identify the total number of pages to retrieve. Alternatively continue to iterate over the query using the $skip keyword until no records or less than 500 (page maximum) are returned.</p><p class="slate-p" placeholder="Type / for widgets">











</p><p class="slate-p" placeholder="Type / for widgets"></p>

Use the HTTP GET method to retrieve data from your workspace via endpoint resources. This includes both lists and individual records. For example, you would use the GET method to retrieve a list of sales orders made in a particular month, or the contact details of a customer. 

By default JSON formatted responses are returned, be sure to use the http header “application/json” when making a request.

Any Date returned in JSON datasets is UTC format represented as 

In order to reduce overall data transfer requirements a record level 

The Datapel API uses the OData standard as the syntax allowing queries of specific data records. By using OData filter queries, you can obtain specific subsets of data, reducing the amount of unnecessary information and enhancing the performance of your workflows.

When using filters, you can use comparison operators like 

, and so on. You can also use logical operators such as 

 to combine multiple conditions. Additionally, there are functions to refine string-based searches. For example, 

 checks if a field starts with a specified string, 

 verifies if a field contains a particular substring.

To explore the syntax and example queries review the OData Standards Support section of this reference guide.

A single HTTP GET request can return at most 500 records. This is reasonable because most HTTP clients have a timeout limit of 2 - 5 minutes. They do not allow transactions to wait more than that. A request running longer than the limit gets an HTTP timeout error. Therefore, it is often required to tune complex queries and lower the data size for them to complete within the timeout restriction. Long running queries can also degrade server response times to other users and tenants so its best practice to do smaller queries more often than large one off data requests

The OData API provides several pagination options for query results.

Client-side pagination uses query options on the client side to create an offset that restricts the amount of data returned from the server.

A client-side pagination query can be made using the following URI parameters:

For example, a query with $skip=2000&$top=500 returns the fifth page of data where the page size is 500.

Considerations when using OData pagination

Most queries will return a total record count which allows your request to select a exact page number, and identify the total number of pages to retrieve. Alternatively continue to iterate over the query using the $skip keyword until no records or less than 500 (page maximum) are returned.

OData is a way to query data sources over the web using a standard syntax. It allows requesting of specific data columns with filter expressions to return required data sets typically in JSON format. Because the OData specification is standardised and ISO/IEC approved, you can theoretically use any OData compliant data source and it will respond in the same way to an OData formatted query.

Parameters are made up of the various OData functions for selecting and filtering entities.

These parameters are chained together after the entity using 

Filters allow you to reduce the data set by specifying a field and a requirement. There are 2 formats for filter:

The correct format to use depends on the operator you are using.

There are other more specific expressions which you can find at the 

Filters can be chained together internally with 

 keyword is not supported, you need to create an expanded filter as (Field 

The convention for field name referencing is based on the JSON response property name. There are some limitations on the scope of filtering by 

 and on how the response is returned. Field name paths are only support for first level child nodes where the property name is not unique, in all other cases child node path is not required.

When filtering on child nodes path elements are only valid to one level, for example 

$filter=parentnode/childproperty eq ‘value1’

 is valid, where the following is not valid as 

$filter=parentnode/childnode/childproperty eq ‘value1’

The orderBy function allows you to specify a sort for your data. The syntax for this is:

Direction is either ascending or descending as shown in these examples:

Top and Skip tend to go hand in hand. Top can be used to limit the number of records returned, while skip allows you to start from further down your list of results. In order to create PAGED results use the top keyword to specify the number of records and skip * page * number of records per page to get the a particular page in the result set.

Datapel API Supports basic OData syntax for keywords 

select, filter, skip, top, order by and apply. 

Aggregations using Odata apply query option is supported.

is the equivalent of the below in SQL for clarity and reference

<p class="slate-p" placeholder="Type / for widgets"><span style="background-color:rgb(255, 255, 255);color:rgb(106, 110, 113);font-size:14px" class="slate-color"><span style="background-color:rgb(255, 255, 255);color:rgb(106, 110, 113);font-size:14px" class="slate-backgroundColor">To simplify web application development OData compliant web components can bind directly to the API endpoint services. For example the DevExpress DevExtreme javascript visual components have OData 2.0 and 4.0 compatible controls. DevExtreme supports a multitude of frameworks including KnockOut, Angular, React and others. The primary adapter for the API was selected as OData to align with the Microsoft Web Services Stack and the ability to standardise the filtering and selection syntax that simplifies SQL translation.</span></span>

For general information on OData compliance <a href="https://www.odata.org/" target="_blank">https://www.odata.org/</a></p><p class="slate-p" placeholder="Type / for widgets">For more information on DevExtreme Web Components please refer to the following <a href="https://js.devexpress.com/" target="_blank">https://js.devexpress.com/</a></p><p class="slate-p" placeholder="Type / for widgets">On OData refer to <a href="https://js.devexpress.com/Documentation/Guide/Data_Binding/Specify_a_Data_Source/OData/" target="_blank">https://js.devexpress.com/Documentation/Guide/Data_Binding/Specify_a_Data_Source/OData/</a></p><p class="slate-p" placeholder="Type / for widgets">For specific connector declaration visit <a href="https://js.devexpress.com/Documentation/ApiReference/Data_Layer/ODataStore/" target="_blank">https://js.devexpress.com/Documentation/ApiReference/Data_Layer/ODataStore/</a></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p>

To simplify web application development OData compliant web components can bind directly to the API endpoint services. For example the DevExpress DevExtreme javascript visual components have OData 2.0 and 4.0 compatible controls. DevExtreme supports a multitude of frameworks including KnockOut, Angular, React and others. The primary adapter for the API was selected as OData to align with the Microsoft Web Services Stack and the ability to standardise the filtering and selection syntax that simplifies SQL translation.



For general information on OData compliance 

For more information on DevExtreme Web Components please refer to the following 

For specific connector declaration visit 

Read and follow the best practices in this topic for optimal OData API performance and a better user experience.

<h2>Bearer Token Authentication</h2><p>Datapel API version 2.0 uses Bearer Token Authentication, a crucial security mechanism that safeguards our API endpoints and ensures secure communication between clients apps and our API servers. This section describes what Bearer Token Authentication is, how it works, and how to manage secure API access.</p><p>Bearer Token Authentication is a </p>

Datapel API version 2.0 uses Bearer Token Authentication, a crucial security mechanism that safeguards our API endpoints and ensures secure communication between clients apps and our API servers. This section describes what Bearer Token Authentication is, how it works, and how to manage secure API access.

Bearer Token Authentication is a widely adopted method for securing APIs, relied upon by countless applications and services across the internet. It offers a robust, standardized approach to verifying the identity of clients attempting to access an API resource. With Bearer Token Authentication, you can establish trust between the API server and its clients, ensuring that only authorized parties gain access while keeping unauthorized users at out.

In this documentation reference, we will cover the following key topics:

The following sections describes our implementation of the Bearer Token Authentication process.

Bearer Tokens are at the heart of Bearer Token Authentication, serving as the digital keys that grant access to API resources. 

A Bearer Token is a type of access token used in authentication protocols, such as OAuth 2.0 and OpenID Connect. It is a string of characters, typically represented as a long, random alphanumeric sequence. Bearer Tokens act as credentials that a client (usually a user or application) presents to an API server when making a request for a protected resource.

Bearer Tokens operate on a straightforward principle: possession of the token equals access. When a client wishes to access a protected resource via an API, it includes the Bearer Token in the request, typically within the HTTP Authorization header. The server receives the token, validates it, and if the token is valid and not expired, it grants access to the requested resource.

One of the advantages of Bearer Tokens is their statelessness. Unlike session-based authentication, where server-side state is maintained for each user, Bearer Tokens require no server-side storage of session data. This makes them highly scalable and suitable for stateless API architectures, such as RESTful APIs.

While Bearer Tokens offer an efficient way to authenticate API requests, they come with security responsibilities. Since anyone in possession of a Bearer Token can access the protected resources, it is crucial to protect these tokens from theft and misuse. Security measures include token encryption, short token lifetimes, and token revocation mechanisms.

Bearer Tokens often contain a payload that carries information about the client or user, such as user roles or permissions. This payload can help your API server make access control decisions based on the token's content.

In summary, Bearer Tokens represent the authorization credentials clients use to access an APIs protected resources. Understanding their structure, how they are transmitted, and their security implications is fundamental to implementing secure and efficient API based Application. 

Token generation and management are critical aspects of Bearer Token Authentication. To ensure the security of the Datapel API our tokens are 256 bit encrypted and have a limited life span of 30 minutes. A refresh token is provided to allow trust renewal by following the Refresh Authentication flow.

The Bearer Token Authorization flow involves a series of steps that allow a client (such as a user or application) to authenticate itself and gain access to protected resources on our API. This flow is based on the OAuth 2.0 framework and is widely used for securing APIs. Here's a step-by-step breakdown of the typical Bearer Token Authorization flow:

<p>Welcome to the Endpoint Resources Listing section of our API reference. This comprehensive guide provides a detailed overview of all available endpoints and resources within our API. Whether you're a developer looking to integrate our services into your application or an experienced user seeking to explore the capabilities of our API, you'll find everything you need to get started and make the most of our platform.</p><p>In this section, you will </p>

Welcome to the Endpoint Resources Listing section of our API reference. This comprehensive guide provides a detailed overview of all available endpoints and resources within our API. Whether you're a developer looking to integrate our services into your application or an experienced user seeking to explore the capabilities of our API, you'll find everything you need to get started and make the most of our platform.

In this section, you will find a structured and organized list of API endpoints, each accompanied by a description of its purpose and usage. We have designed our API with simplicity and flexibility in mind, ensuring that you can efficiently interact with our platform to meet your specific needs.

To streamline your development process, we have categorized the endpoints into logical groups and provided clear explanations of the parameters and data formats associated with each resource. Additionally, you'll find information on authentication methods, response formats, and any specific requirements for using particular endpoints.

Whether you're retrieving data, creating records, or performing complex operations, this Endpoint Resources Listing is your go-to reference for understanding and utilizing our API effectively. Feel free to explore the endpoints that align with your project's goals and requirements, and use this documentation as your trusted companion on your API integration journey.

Please refer to the table of contents or use the search functionality to quickly locate the endpoints and resources that interest you. If you have any questions, encounter issues, or need further assistance, our support team is here to help.

When reviewing the Post or Response Body it is recommended to click the 

option as shown below to display all nodes and properties.

Let's dive in and explore the wealth of possibilities our API offers. Happy coding!

<p class="slate-p " ><span style="color:rgb(51, 51, 51)">See all updates and changes to our API listed by Date.</span>
</p><div class="table-container" style="width:100%;min-width:100%"><table class="slate-table" ><colgroup ><col style="width:12.055837563451776%"><col style="width:11.611675126903553%"><col style="width:0%"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " ><span style="background-color:#FFFFFF;color:#999999">Date</span></h3></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " ><span style="color:#999999">Version</span></h3></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " ><span style="color:#999999">Description</span></h3></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2024-OCT-28</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >2.0.1028</h3></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >New Estimates endpoint added</h3><p class="slate-p " >
<strong class="slate-bold">Endpoint Name : </strong>estimates

<strong class="slate-bold">Change :</strong> Use endpoint to get list of estimated kit and assembly units that can be built based on available component inventory.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2024-AUG-26</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >2.0.0826</h3></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >New JobCodes endpoint added</h3><p class="slate-p " >
<strong class="slate-bold">Endpoint Name : </strong>jobcodes, jobcode

<strong class="slate-bold">Change :</strong> Use endpoint to get list of jobcodes and jobcode by Uid.  </p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2024-JUL-24</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >2.0.0724</h3></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >Documentation clarification</h3><p class="slate-p " >
<strong class="slate-bold">Endpoint Name : </strong>all GET endpoints

<strong class="slate-bold">Change :</strong> Clarification on use cases for <strong class="slate-bold">$apply</strong> with <strong class="slate-bold">$filter</strong> keywords in OData Standards Support sec</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2024-July-12</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >2.0.0712</h3></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >New Location Bin endpoint added</h3><p class="slate-p " >
<strong class="slate-bold">Endpoint Name : </strong>locationbins

<strong class="slate-bold">Change :</strong> Use endpoint to get list of location bins.  </p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2024-July-09</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >2.0.0709</h3></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >New Attachment POST endpoint added</h3><p class="slate-p " >
<strong class="slate-bold">Endpoint Name : </strong>attachment

<strong class="slate-bold">Change :</strong> Use endpoint to add document attachments to products or order transactions.  </p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2024-July-08</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >2.0.0708</h3></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >New WorkspaceOptions endpoint added</h3><p class="slate-p " >
<strong class="slate-bold">Endpoint Name : </strong>workspaceoptions

<strong class="slate-bold">Change :</strong> This endpoint provides configuration and workspace setting information.  </p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2024-July-06</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >2.0.0706</h3></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >New AuditEvent POST endpoint added</h3><p class="slate-p " >
<strong class="slate-bold">Endpoint Name : </strong>auditevent

<strong class="slate-bold">Change :</strong> This endpoint is designed to allow integration developers to provide status, security, error and warnings directly to the audit list within the customer workspace.  </p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2024-July-03</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >2.0.0704</h3></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h3 class="slate-h3 " >Notice on property retirement</h3><p class="slate-p " >
<strong class="slate-bold">Endpoint Name : </strong>Inward Order List

<strong class="slate-bold">Property : </strong><code class="slate-code"><strong class="slate-bold">InvoiceNumber</strong></code>

<strong class="slate-bold">Change :</strong> This field causes confusion between Despatch and Sale Order properties and intended as Supplier Invoice Number or Supplier Reference Number. To address the ambiguity the field will be renamed to <code class="slate-code"><strong class="slate-bold">SupplierNumber</strong></code>. The InvoiceNumber field will no longer be available from <strong class="slate-bold">2025-1-1</strong>. In the meantime, both SupplierNumber and InvoiceNumber will be available from the endpoint however it has been removed from the documentation to avoid new builds incorporating retired properties.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ></p></td></div></tr></tbody></table></div><p class="slate-p " >













</p><p class="slate-p " ></p><p class="slate-p " ></p>

See all updates and changes to our API listed by Date.