Prerequisites

Prev Next

To successfully integrate with the Wasabi AiR REST API, you must meet several prerequisites. These include understanding the API's functionality, authentication methods, data formats, and how to handle errors. You also need the necessary tools and knowledge to make API requests and process responses.

Understanding the API and Requirements

  • API Documentation: Thoroughly review the API's documentation provided by the API provider. This documentation outlines the API's functionality, supported operations (such as CRUD - Create, Read, Update, Delete), available resources, data formats, authentication methods, rate limits, and error handling mechanisms.  

  • API Functionality: Identify the specific functionalities needed from the API and how they align with your integration requirements.

  • Data Formats: Determine the expected data formats for requests and responses (for example, JSON, XML).

  • Resource Model: Understand how the API organizes its resources and how to interact with them through URIs (Uniform Resource Identifiers).

  • Authentication: Determine the authentication method required by the API (such as API keys, OAuth) and how to implement it.

  • Rate Limits: Understand the API's rate limits (the number of requests that can be made within a specific time period) to avoid exceeding them and causing issues.

  • Error Handling: Learn how the API signals errors and how to manage them effectively.  

Development Environment and Tools

  • Programming Language: Choose a programming language that supports making HTTP requests and handling JSON data.

  • API Client Libraries: Use API client libraries specific to your programming language to simplify API interactions.

  • API Testing Tools: Use tools like Postman or cURL to test API requests and responses before integrating them into your application.

Security Access

  • Access keys: Before interacting with the API, Wasabi access keys must be created and used in the integration. Below is information about these keys and security considerations. If you have questions, refer to the Wasabi Academy article about Wasabi Keys. Include the following policies when creating keys:

    • WasabiAiRFullAccess policy: READ/WRITE operations in console buckets/objects.

    • WasabiAiRReadOnly policy: No POST, can get job details.

    • Administrator Access: Include WasabiAiRFullAccess permissions.

Testing and Monitoring

  • Sandbox Environment: Use the API provider's sandbox or testing environment to thoroughly test your integration before deploying it to production.

  • Load Testing: Perform load tests to ensure the integration can handle a high volume of requests.

  • Monitoring: Continuously monitor the integration in production to identify and address any issues that may arise.