1. Welcome to ApplicaDigital

ApplicaDigital is an initiative by PDI Consultores, designed to empower publishers, corporations, and libraries seeking the most secure and professional way to commercialize, distribute, or lend digital publications.

Our focus is on the secure distribution of digital content in ePUB and PDF formats, ensuring the protection of copyright and the integrity of your intellectual property.

1.1. First Steps: Initial Checklist

To start using ApplicaDigital effectively, we recommend following these initial steps:

• Review your credentials: Make sure you have your access URL, username, and password provided by our team readily available.
• Familiarize yourself with the panel: Take a few minutes to explore the different sections, starting with the Available Catalog to view your publications.
• Configure default permissions: Before performing bulk uploads, visit the Permissions Settings section. This step is crucial.
• (For developers) Download the Postman collection: If you plan to integrate ApplicaDigital via our API, we recommend downloading our Postman collection to facilitate testing.
• Consult this guide: Use the navigation menu to quickly find the information you need.

2. How to use this guide

This guide is designed as a comprehensive reference resource. Use the floating navigation menu on the left to quickly jump to the section you need.

3. Technology Used

The platform uses Adobe Content Server (ACS), the reference technology in digital rights management (DRM). ACS allows securely distributing eBooks and documents in PDF, ePUB, ePUB2, and ePUB3 formats through the market's most robust encryption.

The files, once protected, are compatible with the Adobe ecosystem, primarily through the free viewer Adobe Digital Editions (ADE), ensuring a standardized and reliable user experience.

4. Panel User Guide

4.1. Access and Test Environment

To access the panel, use the credentials (URL, username, and password) provided by our support team: soporte@applicadigital.com.

4.2. Available Catalog

This is the main view of your panel. It shows all your encrypted publications, allowing you to manage your digital inventory at a glance.

4.3. Upload and Update Books

This section allows you to add new publications to your catalog or modify existing ones.

4.4. View Downloads

Records each time an end-user opens a protected book for the first time. This screen is your audit and support tool.

4.5. File History

Shows a detailed log of all operations performed on a file: upload, update, deletion, and the result of each process.

4.6. Permissions Settings

Here you define the default permissions that will be applied to bulk uploads. It is a key section for automating your workflow. It is highly recommended to review and understand each available permission option to ensure your publications are distributed according to your specific needs.

(Consider adding a detailed table or a broken-down list of all available permissions and their implications here.)

5. API Documentation

Our REST API allows you to automate every aspect of publication management, integrating ApplicaDigital directly with your e-commerce, ERP, or management system.

5.1. Access and Authentication

To start, generate your credentials in Settings → API Access. All requests must use Basic Authentication (Basic Auth) and be of type POST.

5.2. Endpoint: getCatalog

Retrieve your publication catalog.

Copy<request>
    <catalogType>resume-xml</catalogType>
</request>

5.3. Endpoint: getDownloadLink

Generate the download link (.acsm file) for an end-user.

Copy<request>
    <typeID>uuid</typeID>
    <bookID>urn:uuid:12345-abcde-67890</bookID>
    <transID>SALE-2025-4567</transID>
    <transType>buy</transType>
</request>

5.4. Endpoint: getDownloads

Consult the download log.

Copy<request>
    <searchType>bytransid</searchType>
    <transid>SALE-2025-4567</transid>
</request>

5.5. Endpoint: addBook

Upload and encrypt a new book programmatically. The Content-Type must be multipart/form-data.

Refer to the complete Postman documentation for an example of this request.

5.6. Endpoint: updateBook

Update an existing book. Requires an additional mandatory parameter: uuid, which must contain the book's ResourceID.

Refer to the complete Postman documentation for an example of this request.

Questions about the API or found an error? Contact our support team.

6. Common Troubleshooting

Why is my bulk or FTP upload failing?

The most common cause is not having configured "Default Permissions" in the Settings panel. This is a mandatory step for bulk uploads.

A client says they cannot download a book. What do I do?

Go to "View Downloads" and search by their purchase transaction ID. You can verify if the link was already used, from which IP, and on what date. This will give you all the information to assist them.

I have updated a book, but my clients are still seeing the old version.

Updates only apply to new downloads. A user who already had the book on their device will retain the original version. To force an update, they would need to delete their local copy and re-download it.

7. Glossary of Terms