Git Product home page Git Product logo

fireblocks-openapi-spec's Introduction

Fireblocks OpenAPI Specification

This repository contains the Fireblocks OpenAPI specification used to generate the API Reference on the Developer Portal.

fireblocks-openapi-spec's People

Contributors

asudimac avatar aviba avatar barakfireblocks avatar dsahni avatar itayfireblocks avatar lazars14-f avatar slavasereb avatar trevordixon avatar vsiskin avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar

fireblocks-openapi-spec's Issues

Feature Request: Implement Disable and Delete Actions for /management/users Endpoint

Description:
To enable comprehensive and automated user lifecycle management, it is essential to have the capability to disable and/or delete users via the /management/users endpoint. Currently, the absence of these actions hinders effective management and automation of user accounts.

Feature Request:

Disable User Action: Add support for disabling user accounts. This action should prevent disabled users from accessing their accounts while retaining their data and settings, allowing for potential reactivation in the future.
Delete User Action: Add support for deleting user accounts. This action should permanently remove the user’s data and access privileges from the system.
Use Case:
Automated user lifecycle management involves creating, updating, disabling, and deleting user accounts based on their status within an organization. The ability to disable or delete users through the API will streamline this process, reduce manual intervention, and improve security by ensuring that inactive or former users no longer have access.

Benefits:

Enhanced Security: Prevent unauthorized access by former employees or inactive users.
Operational Efficiency: Automate user management tasks, reducing the need for manual intervention.
Compliance: Ensure compliance with organizational policies and regulations regarding user access and data management.
Thank you for considering this feature request.

Replace 5XX to actual errors

Some Swagger generting clients treat status code as integer and hence unexpect to see 5XX as string. Example here

Think it's even safe to skip those errors in the annotations

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.